Am I right in thinking that you might need either

key-properties

or

table-key-properties

in your metadata depending on what version of

singer-sdk

a particular tap uses?

Hmm, that'd be unexpected. The SDK looks the for the

key_properties

override at the catalog entry level:

{
  "streams": [
    {
      "tap_stream_id": "example",
      "schema": {...},
      "metadata": [...],
      "key_properties": <------------ HERE
    }
]

I was using

tap-tiktok-business

which specifies

singer-sdk=0.4.x

in pypoetry.toml. I thought that at some point the naming system changed in

singer-sdk

so

key-properties

became table/view-key-properties. Could be completely wrong though

Hmm, not really or at least not since

v0.4.0

so it should be the same as today