Hi! We're experiencing some syncing issues with `s...
# replication-troubleshooting
h
Hi! We're experiencing some syncing issues with
source-postgres==1.0.39.
We're syncing incrementally on an
updated_at
column that can contain null values and consistently see newly created records with
updated_at==NULL
being skipped. This may be the expected behavior? Is there anything we can do to get around that and sync new data without losing the ability to get updated versions of records? Thanks in advance for your help 🙏
u
Henri this was not happening using a previous version? Did you try the latest version https://github.com/airbytehq/airbyte/pull/21523 probably fix some problems with null cursor values.
h
@Marcos Marx (Airbyte) thanks for the help. When updating
source-postgres
to
>1.0.42
I get:
Copy code
Additional Failure Information: io.airbyte.commons.exceptions.ConfigErrorException: The following tables have invalid columns selected as cursor, please select a column with a well-defined ordering with no null values as a cursor. {tableName='public.my_table', cursorColumnName='updated_at', cursorSqlType=TIMESTAMP, cause=Cursor column contains NULL value}
m
@Rodi (Airbyte) do you have any comment here to help Henri? I saw you introduced the message error here. The Postgres connector doesn’t support null cursor columns anymore?