Connector Improvement: Snowflake Connector Improvement - Feature flag to compute _fivetran_id on fivetran for non-cdc connectors
Not plannedAs discussed on Unknown failure. String is too long and would be truncated – Fivetran Support
We intermittently encounter String too long errors on our connectors that have tables/CDC which do not support CDC.
A feature flagged was turned on to handle tables that support CDC.
Statement from the support case # 227103:
Our Engineering team has advised that we should continue to avoid enabling the Feature Flags for the requested connectors for the following reasons:
Under this Feature Flag, we will compute the hashID (_fivetran_id) on our end instead of in your Snowflake database.
For your connectors, the team has successfully tested this method for CDC-based syncs only.
Currently, this approach has not been implemented for teleport-based syncs.
The team does plan to test this method for teleport-based syncs; however, we do not have an estimated timeline for the completion of this testing at this moment.
We apologize for any inconvenience this may have caused and appreciate your patience as we work to improve our service.
Please don't hesitate to let us know if you have any further questions or concerns.
-
Official commentHi Joel,Thanks for the idea! While it’s not currently planned, we’re actively tracking interest via votes and comments. Please continue to share your use cases. Strong demand enables us to prioritize features that deliver the greatest value to our customer community.Best regards
Please sign in to leave a comment.
Comments
1 comment