Joel Santiago
- Total activity 18
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 2
- Subscriptions 7
Posts
Recent activity by Joel Santiago-
Connector Improvement: Fix limitation on Databricks Connector for large STRING data
CompletedThis relates to this support ticket Databricks to RDS Error - Required array length 2147483639 + 158 is too large – Fivetran Support From the ticket we found that fivetran has a limit on the STRING...
-
Connector Improvement: Fail Connector If Changes are too big for Teleport instead of Quarantining Silently
Not plannedPreviously, we were sync-ing tables using teleport and regardless of the size, teleport sync was attempted and then it could run for a long time and eventually fail. We see that this behavior has c...
-
Destination Improvement: Support Delta Lake Variant Datatype for Databricks
Not plannedWe have a Snowflake Connector that syncs data to a Databricks Destination. Majority of the source tables have variant columns. These are currently being casted to Fivetran String to Databricks Stri...
-
Connector Improvement: Explicit Failure / Reschedule when a table switches from timetravel to teleport
This is from the fivetran support case - Data mismatch between snowflake and databricks – Fivetran Support Following an internal review by the engineering team, it has been determined that the sys...
-
Connector Improvement: Functionality to force the table to do a teleport sync even if timetravel is possible
We have a use case where we have a source owned by a vendor. We are sync-ing some tables that are being truncated and reloaded every batch run. The source database is snowflake. Change tracking is...
-
Other: Capability to list all the feature flags set for a connector
AnsweredWe have been seeing varying behavior on fivetran despite using the same source. It is difficult to diagnose issues and reasons for differences in behavior. We have raised at least 2 fivetran ticke...
-
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 ...