Unparseable date with Postgres source connector 0.4.19

[remisalmon]

Environment

• Airbyte version: 0.38.4-alpha
• OS Version / Instance: AWS EC2
• Deployment: Docker
• Source Connector and version: Postgres 0.4.19
• Destination Connector and version: Snowflake 0.4.26
• Step where error happened: Sync job

Current Behavior

Incremental syncs are failing after updating the Postgres connector to 0.4.19.

The timestamp format (cursor) went from being in the 2022-05-27T17:48:56.925922Z format to 2022-05-31T20:23:494 in Snowflake, and cannot be parsed by the Postgres source connector.

Expected Behavior

Timestamps with no timezone should be parsed by the Postgres source connector.

Logs

2022-06-01 15:20:40 �[44msource�[0m > 2022-06-01 15:20:39 �[1;31mERROR�[m i.a.i.b.AirbyteExceptionHandler(uncaughtException):26 - Something went wrong in the connector. See the logs for more details.
2022-06-01 15:20:40 �[44msource�[0m > java.lang.RuntimeException: java.text.ParseException: Unparseable date: "2022-05-31T20:23:494"
2022-06-01 15:20:40 �[44msource�[0m > 	at io.airbyte.db.jdbc.AbstractJdbcCompatibleSourceOperations.setTimestamp(AbstractJdbcCompatibleSourceOperations.java:167) ~[io.airbyte.airbyte-db-lib-0.39.5-alpha.jar:?]

Steps to Reproduce

1. Setup a Postgres source 0.4.19 with incremental sync + deduped history and Snowflake destination 0.4.26
2. Sync
3. Sync again: failure

Are you willing to submit a PR?

No.

[keurcien]

Not sure if this is related, but it also happened to me after updating to 0.4.19 (using a Postgres destination):

• Incremental + Append from a Postgres DB to another Postgres DB
• FIrst sync works
• Subsequent syncs fail raising: TIMESTAMP WITH TIMEZONE is not supported.