Hi all - I'm having some some trouble with incremental data loads using the airbyte wrapper tap. It seems to support it - albeit with a fork at the moment that implements a necessary fix - but I can't seem to get it configured to use incremental. The tap supports it, as does the airbyte docker image itself, but the

CatalogEntry

that the wrapper uses to determine the sync mode has

replication_method='FULL_TABLE'

stuck on, and I can't seem to force it to go to incremental. My tap is set up with:

- name: tap-az-interchange
    inherit_from: tap-airbyte-wrapper
    metadata:
      '*':
        replication-method: INCREMENTAL
        replication-key: _ab_source_file_last_modified
    select:
    - stream1.*
    config:
      airbyte_spec:
        image: airbyte/source-azure-blob-storage
        tag: latest
      airbyte_config:
        streams:
        - name: stream1
          globs:
          - test/file/path/here
          format:
            filetype: jsonl
        start_date: '1900-01-01T00:00:00.000000Z'
        azure_blob_storage_account_key: $TAP_AZ_INTERCHANGE_AIRBYTE_CONFIG_AZURE_BLOB_STORAGE_ACCOUNT_KEY
        azure_blob_storage_container_name: azure-container-name

At the moment, but I'm not at all sure I have it set up correctly, especially not the

metadata

block. Can anyone point me in the right direction? I have the airbyte wrapper checked out locally so that I can log out all the inputs to it and debug what's going on. When I run the job, I get

Beginning full_table sync of 'stream1'...

every time too.,

Hey @Alex Maras any luck on this? I recently encountered the same issue

Filed an issue and also sent a PR that fixes it: https://github.com/MeltanoLabs/tap-airbyte-wrapper/issues/14

Thanks @jichao_sun - I had a less comprehensive PR for that - https://github.com/MeltanoLabs/tap-airbyte-wrapper/pull/12 I can close that off now.