Hello, Anyone faced issues with

forced-replication-method

? Specifically, in

tap-zendesk

even when defining in

meltano.yml

metadata:
  groups:
    replication-method: FULL_TABLE

the

forced-replication-method

property in the catalog file forces the replication method to be

INCREMENTAL

. We automatically generate the

catalog

and here’s how the

groups

stream is defined:

{
  "breadcrumb": [],
  "metadata": {
    "table-key-properties": [
      "id"
    ],
    "forced-replication-method": "INCREMENTAL",
    "valid-replication-keys": [
      "updated_at"
    ],
    "selected": true,
    "replication-method": "FULL_TABLE"
  }
}

so the

replication-method

was correctly picked-up from our

meltano.yml

file, but it’s being overridden by

forced-replication-method

(which we didn’t define anywhere).

@benjamin_maquet If tap-zendesk is setting its

forced-replication-method

to

INCREMENTAL

and ignoring your override, I suggest taking the hint 😄 The code here strongly suggests that the tap simply doesn't support FULL_TABLE replication for this stream: https://github.com/singer-io/tap-zendesk/blob/db707dab53e9084e7165a9768723be412e37e270/tap_zendesk/streams.py#L415-L429 If you want to always load that entire table, you'll have to implement support for both methods on the tap

thanks for the pointer! I’ll indeed take the hint and use incremental.. 🙂