Instead of relying on the connector to interpret the CHAR(36)
column, you could cast the CHAR(36)
column explicitly to a string in the MySQL query itself. For example:
SELECT CAST(your_column AS CHAR) AS your_column FROM your_table;
If casting in the query isn't sufficient, consider creating a view or a temporary table that already has the CHAR(36)
column cast as a string and use that in your data pipeline.
Another approach is to handle this transformation directly in Synapse, using a data flow where you map the CHAR(36)
column explicitly as a string.
Given that this could be a bug in the connector, it might be worth raising a formal support ticket with Microsoft to have this issue investigated and potentially fixed.
If none of these workarounds are suitable for your environment or you continue facing issues, you may want to consider this as a temporary issue to escalate to Microsoft while keeping the current workaround in place.