https://linen.dev logo
#troubleshooting
Title
# troubleshooting
s

Srinivasula Reddy Yennapusa

03/01/2022, 6:21 AM
Ask for help submission from @Gary K *Is this your first time deploying Airbyte * No *OS Version / Instance * Debian GNU/Linux 11 (bullseye) *Memory / Disk * left blank *Deployment * Kubernetes *Airbyte Version * 0.35.42-alpha *Source name/version * MySQL, 0.5.6 *Destination name/version * Postgres, 0.3.15 *Step * Mid-sync *Description * In the middle of a sync it errors out. All tests are ok, and a lot of data is transferred, but at what looks like the same point it just stops with no reason (apart from exit code 1). Normalisation occurs without error. The row size is small, and I've checked the data in the table where it stops without noticing any bad data weirdness. Any ideas on where/what to look at here?
u

user

03/01/2022, 6:25 AM
The logs for the three attempts.
u

user

03/01/2022, 6:25 AM
🥺 🙏
g

Gary K

03/15/2022, 10:45 PM
Finally discovered the problem, which was a date column containing zero day values, ie
2003-01-00
. Note that the mysql source connecter adds the zeroDateTimeBehavior=convert_to_null property and zero dates (
0000-00-00
) are being converted to null correctly; the issue is when a value that is NOT a zero date (
0000-00-00
) has a zero day (
2003-01-00
).
I'm thinking that an error log in the source connector would have made this a lot easier to find instead of a silent exit code 1 🤪😝
4 Views