I’ve just upgraded the mysql source from `0.6.12` ...
# ask-community-for-troubleshooting
g
I’ve just upgraded the mysql source from
0.6.12
to
1.0.1
(GA i believe) and it seems a mess. Running into production syncing issues now • cannot handle separate streams;
Cannot *drop*
*column* '_AIRBYTE_UNIQUE_KEY' which belongs *to* a clustering key
Numeric value 'true' *is* not recognized
in the SCD normalization process. i’ve created issues here and here. But the most pressing issue is that we can’t revert back to
0.6.12
without still experiencing the same issue across all connectors
✍️ 1
u
@[DEPRECATED] Marcos Marx turned this message into Zendesk ticket 2519 to ensure timely resolution!
s
Hey @gunu, I created an issue on our Github with this ticket: https://github.com/airbytehq/airbyte/issues/17510 The MySQL connector is not in GA, it’s just about to be in beta.
g
i think this one is actually an issue with the destination - snowflake
e
Hi! do you have any update regarding this issue, i am also getting Cannot drop column '_AIRBYTE_UNIQUE_KEY
s
Hi @Elizabeth Rodriguez, feel free to make a new thread with your issue! At the moment, I don't believe this has been solved yet but there's a discussion in one of our PRs: https://github.com/airbytehq/airbyte/pull/14424#issuecomment-1266351233
g
@Saj Dider (Airbyte) i raised two issues, i think @Elizabeth Rodriguez is having issues with the first one - relating to separate streams (
_AIRBYTE_UNIQUE_KEY
) and not the latter (the tinyint / Numeric value one)
@Elizabeth Rodriguez the UNIQUE KEY issue discussed here: https://discuss.airbyte.io/t/mysql-1-0-1-fails-to-handle-separate-streams/2774