Area: Ingestion
Sub-Area: Fivetran
Issue
Fivetran ingestion sources that were previously working begin failing after a DataHub version upgrade, preventing metadata about Fivetran pipelines and data transformations from being ingested.
Solution
Note: For DataHub Cloud customers, infrastructure-level changes are managed by DataHub Support.
Verify Fivetran connector compatibility:
- Check DataHub release notes for Fivetran connector changes
- Fivetran connector may require recipe format updates after DataHub upgrades
- Review breaking changes in the version you upgraded to
Update Fivetran recipe configuration:
source:
type: fivetran
config:
fivetran_api_key: "${FIVETRAN_API_KEY}"
fivetran_api_secret: "${FIVETRAN_API_SECRET}"
# May need to add after upgrade:
destination_platform: "snowflake" # or your target platform
destination_platform_instance: "prod"
Check Fivetran API permissions:
- Ensure API key still has necessary permissions
- Verify API key hasn't expired
- Test Fivetran API access using curl or Postman
Contact support for cloud customers:
- Provide before/after DataHub versions
- Share ingestion error logs
- Support can validate connector compatibility and configuration
Additional Notes
Test configurations in a development environment before applying to production. Always backup configurations before making changes.
Related Documentation
Related Tickets
- 5839
Tags:
fivetran, etl, version-compatibility, troubleshooting