java.lang.RuntimeException: java.time.format.DateTimeParseException: Text '0' could not be parsed at index 0

[mkhokh-33]

created issue from @danieldiamond comment ralated to RP - #15504
A couple of people running into issues now
java.lang.RuntimeException: java.lang.RuntimeException: java.time.format.DateTimeParseException: Text '0' could not be parsed at index 0

e.g.

• myself with source MySQL from 0.6.2 -> 0.6.4 (I'm using CDC). confirmed that syncs work again when reverting back to 0.6.2
• someone in disourse Potgres sync fail after update 0.4.0 -> 1.0.2
• and someone else in slack

[subodh1810]

This seems relevant

The thing is it happens only in incremental mode (I don’t get the issue in full refresh mode).
One column has a default value set as CURRENT_TIMESTAMP(0) and this is slightly different from other tables that have a default value set as CURRENT_TIMESTAMP
Could it be the root cause ?

[grishick]

@mkhokh-33 This is likely to cause a P0 outage, so please take this into implementation ASAP prioritizing above the other issue that you have in review currently.

[ryankfu]

@mkhokh-33 it seems the likely culprit is actually related to this PR: https://github.com/airbytehq/airbyte/pull/15504/files since this was not added to the change log but it touched MySQL. There may be another PR that touched Postgres but this is where the team seems to think the issue arose

[subodh1810]

@danieldiamond
I am not able to reproduce this for mysql or postgres. I tried to sync data from a mysql table with the following structure in CDC mode and it worked perfectly fine

create table test(id int primary key, updated_at timestamp(0) not null default CURRENT_TIMESTAMP(0), updated_at_2 timestamp(1) not null default CURRENT_TIMESTAMP(1), updated_at_3 timestamp(2) not null default CURRENT_TIMESTAMP(2), updated_at_4 timestamp(3) not null default CURRENT_TIMESTAMP(3), updated_at_5 timestamp(4) not null default CURRENT_TIMESTAMP(4), updated_at_6 timestamp(5) not null default CURRENT_TIMESTAMP(5));

can you share the schema of the table for which you faced the error and logs from the sync

[mackro-rocky]

We're seeing the same issue on postgres with 1.0.2 connector.

Logs attached
logs-56.txt

[subodh1810]

hey @mkhokh-33 FYI, am already working on fixing this.

[subodh1810]

Postgres error should be fixed by this PR #15877

[subodh1810]

MySQL error should be fixed by this PR #15917

[subodh1810]

This has been fixed for both postgres (in version 1.0.4) and MySQL (in version 0.6.5), closing the issue