Summary
Airbyte UI in version v1.1.0 does not have logical replication selection despite it being mentioned in the developer guide. User is inquiring about the reason for this discrepancy.
Question
in the developer guide its says enable logical replication
but in the airbyte ui there is no logical replication selection
airbyte version v1.1.0 can i know why is that
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["logical-replication", "airbyte-ui", "developer-guide", "version-v1.1.0"]
Docs are not consistent with a form. This is the same CDC
I created a pull request for that https://github.com/airbytehq/airbyte/pull/47348
Means there is not problem in the feature only the wordings?
If you read further, then you have in CDC section
> Airbyte uses <https://www.postgresql.org/docs/10/logical-replication.html|logical replication> of the Postgres write-ahead log (WAL)
Description matches option Read Changes using Write-Ahead Log (CDC)
Ok got it thank you so much , one more thing d i fallowed rhe exact thing and when i create the source using Read changes using WAL i am only getting full sync append and overwrite not the incremental why do you know why
Few things:
• you need to double-check all the steps
• you need to restart database
Also,
I’d Retest saved source
on Settings tab for source and I’d Refresh source schema
on Schema tab on connection page
you can also run this query to verify if your tables are properly configured
tab.table_name,
tco.constraint_name,
string_agg(kcu.column_name, ', ') as key_columns
from information_schema.tables tab
left join information_schema.table_constraints tco
on tco.table_schema = tab.table_schema
and tco.table_name = tab.table_name
and tco.constraint_type = 'PRIMARY KEY'
left join information_schema.key_column_usage kcu
on kcu.constraint_name = tco.constraint_name
and kcu.constraint_schema = tco.constraint_schema
and kcu.constraint_name = tco.constraint_name
where tab.table_schema not in ('pg_catalog', 'information_schema')
and tab.table_type = 'BASE TABLE'
group by tab.table_schema,
tab.table_name,
tco.constraint_name
order by tab.table_schema,
tab.table_name;```
Thank you <@U05JENRCF7C>
i rechecked and the table was missing primary key added now i am able to see the incremental sync