Henri Blancke
02/06/2023, 6:48 PMsource-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 🙏user
02/07/2023, 10:35 AMHenri Blancke
02/08/2023, 4:04 PMsource-postgres to >1.0.42 I get:
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}Marcos Marx (Airbyte)
02/08/2023, 9:29 PM