Skip to main content

Community

Connector Improvement: Fivetran is changing data types between same source & target for no reason

Answered

Please sign in to leave a comment.

Comments

2 comments

  • Official comment

    Hi Sudhir,

    This connector improvement is not currently on our roadmap. Today, we convert data types to our platform’s standard types to ensure compatibility with the selected destination—especially when it differs from the source. We do understand that in your case, the source and destination are the same, which makes this behavior less ideal.

    Feature prioritization is guided by community interest and upvotes. Each upvote on this request strengthens the case for consideration. Additionally, sharing more details about your specific use case—and the impact of converting ARRAY to VARCHAR in your environment—would help us better assess the need and justify future investment.

    Best regards,

    Hi Egidio,

    If downstream logic is written considering source column is ARRAY then they would expect same datatype in target specially when source and destination both systems are Snowflake databases.
    Ex. Business wrote their logic using some native array functions in snowflake but it failed as Fivetran converted ARRAY to VARCHAR on it's own. I could have understood this if source and destination systems are different and fivetran uses native datatypes to manage compatibility between systems but for same type of source & destinations, This is a surprise to end users and also a bad user experience. Even old database replicators like Oracle GoldenGate used to take care of this seamlessly and I believe Fivetran being a modern replicator platform should have this feature too.   Thank you.