- Is this your first time deploying Airbyte?: No
- OS Version / Instance: Ubuntu
- Memory / Disk: 64Gb
- Deployment: Docker
- Airbyte Version: 0.40.14
- Source name/version: MySQL 1.0.3
- Destination name/version: Snowflake 0.4.38
- Step: First sync, normalization issue
Numeric value 'false' is not recognized
How does this happen with GA connectors? This is a fresh new deployed airbyte instance, this is the latest source and destination versions and the first sync for this table.
d39daee2_294b_4e75_8522_740f14df7112_logs_48424_txt.txt (167.8 KB)
It seems the staging view (the automatically generated staging view as part of the incremental + dedupe normalisation process) is the source of the issue. I cannot view it in snowflake
Hi @danieldiamond, I think this is due to new updates to the MySQL connector and how it handles boolean values. I’ll have more info for you in a bit below!
First a few questions:
What is the field type for the value causing the error, is it Boolean or TINYINT?
What version of the MySQL connector were you using before this that did not cause errors?
And some information:
There is a GitHub issue for this here, it is not resolved yet:
We changed how the MySQL source connector returns booleans some time between 0.6.1 and 1.0.1.
A potential workaround would be to roll back the version to 0.6.15.
Another two workarounds are described here:
This is actively being worked on let me know if any of those 3 workarounds pan out for you!
- The field in MySQL source is
tinyint(1) unsigned and in the staging view it’s
) as MY_FIELD
and in the RAW AIRBYTE table the JSON is
- i think the MySQL connector version was
Got it, thanks!
Could you try rolling back to a pre 1.x.x version, using one of the work arounds listed in the link below, or doing a total reset? The reset obviously would be a last resort option.
Is the suggestion to migrate to pre 1.X OR reset the connector? Because this is a brand new connector, never been synced. Resetting doesn’t resolve this issue
Oh, I see I wasn’t aware that there was already a discussion happening on GitHub! I see that one of our engineers is looking for more info for you here:
Sorry for the confusion - in this case please try rolling back to
0.6.15 or below, that should be the temporary workaround. Let me know if that helps! Otherwise I’d say to keep an eye on that GitHub thread!
Hey Daniel, it looks like the issue has been solved! Let me know if you need any further info!
Yes @natalyjazzviolin, subodh crushed it. He was extremely responsive, investigated the issue thoroughly and provided a timely and solid fix. Big fan, airbyte team lucky to have him.