💪 Did you know? Fivetran has deprecated its Metadata API and released a more comprehensive Platform Connector. Atlan recommends transitioning to the Fivetran Platform Connector in Fivetran for seamless metadata enrichment in Atlan. For any existing Fivetran workflows, you can migrate to the Fivetran Platform Connector in Fivetran first and then modify the crawler configuration in Atlan to update the extraction method.
What are the known limitations of the Fivetran connector?
Atlan currently does not support the following:
- There are two types of alerts in Fivetran — errors and warnings. While errors are supported with the Fivetran Platform Connector package, warnings are currently not supported.
Why is lineage missing?
If you notice any Fivetran lineage missing in Atlan after migrating to the Fivetran Platform Connector in both Fivetran and Atlan, following may be the possible causes:
- Atlan generates lineage based on the metadata received from the Fivetran Platform Connector tables stored in a warehouse. Any changes in lineage after the migration are likely due to how Fivetran provides lineage metadata for the Fivetran Platform Connector as opposed to the Metadata API.
- If any Fivetran Platform Connector tables or schema are dropped or renamed in the destination warehouse, then Fivetran will recreate them with the original names in the next sync. However, it will only add any new incremental data. To access the historical data or fix any data integrity issues, you may need to trigger a re-sync. Refer to Fivetran documentation to learn more.
Why is click-through to Fivetran not working?
If you click View in Fivetran in Atlan and you are redirected to the Fivetran homepage, then you may not have the necessary permissions in Fivetran to view the connector. You will need to have at least a Connector Reviewer role or any other role hierarchically above that to view Fivetran connectors.