Hey y’all! I’m working on creating a new destination connector and would like it to support CDC and incremental append sync mode. I’m a little confused about what is entailed to support CDC. 1. It appears from the example in the overview doc that you just add a boolean delete field to records in the destination. Is that correct? Is it expected that all destination connectors handle CDC correctly? I didn’t see it in the spec docs. 2. In this post it says that incremental append sync mode requires dbt support, but the docs linked don’t mention that. Is dbt support required to implement append sync for a destination connector? EDIT: I found a bunch of destination connectors in the repo that have

supportsDBT: false

and support

append

sync mode, so I think that blog post is just outdated.

Thread sent successfully to Harvestr

1. all destination supports CDC because they will receive an AirbyteRecord object to ingest. You need to make sure your destination supports the default (id, data, emmited_at) fields. 2. you can make your destination supports Incremental Append mode but for Incremental Dedup + history mode you must have dbt module to execute this step

Thanks!

Feedback was linked to Destination Contribution DX

Linked feedback:

Hey y’all! I’m working on creating a new destination connector and would like it to support CDC and incremental append sync mode. I’m a little confused about what is entailed to support CDC.

1. It appears from the example in the overview doc that you just add a boolean delete field to records in the destination. Is that correct? Is it expected that all destination connectors handle CDC correctly? I didn’t see it in the spec docs.

2. In this post it says that incremental append sync mode requires dbt support, but the docs linked don’t mention that. Is dbt support required to implement append sync for a destination connector?