Limitations and Troubleshooting¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Limitations¶
If the transformation or orchestration job contains a query that has a two-part name (schema.table) for 3-part (catalog.schema.table) Alation-supported datasources, then lineage will not appear. Because Alation supports 3-part schema names and thus cannot resolve the lineage.
Cross-system lineage will not be generated due to parsing issue on Matillion side, where square brackets, or non-standard SQL queries are not parsed by the Matillion parser correctly.
Troubleshooting¶
For information about logs, refer to Troubleshoot OCF Connectors.
Find specific troubleshooting scenarios below:
Long Runtime During Lineage Extraction¶
Problem¶
Lineage extraction from Matillion is taking a long time to complete.
Solution¶
Lineage extraction duration can be delayed if the Lineage lookback (days) is set to a high value. By default lookback time set to 30 days after first run, you can set this to lower days and schedule an extraction.
Cross-System Lineage Fails to Generate¶
Problem¶
Cross-system lineage is not generated after configuring Matillion lineage settings.
Solution¶
Cross-system lineage generation fails if the hostname and port do not match between Matillion and Alation data source configuration. Ensure that the host and port information in the Additional Datasource Connections field matches the Matillion configuration. For more information, refer to Configure Lineage Across Data Sources in Configure Lineage.