Skip to main content

Lineage

Answers to common questions about how Atlan calculates lineage from Talend jobs and components.

How does Atlan calculate lineage from Talend?​

The connector statically analyzes Talend project files. It parses SQL queries from database components, analyzes tMap field expressions, and traces data flow through component connections to create lineage relationships in Atlan. Lineage is calculated for direct column mappings, SQL transformations, component field expressions, and multi-hop transformations through multiple components.

Why is lineage missing for tJavaRow components?​

tJavaRow contains custom Java code that can't be automatically parsed for lineage. Column-level lineage may not be captured through tJavaRow transformations. To document the transformation logic, use descriptive component names and add detailed descriptions in Talend Studio.

What Talend components and scenarios don't support lineage?​

The connector can't extract lineage for:

  • Custom routines: Java routines and custom functions with dynamic logic
  • Dynamic schemas: Components with schema definitions resolved at runtime
  • External transformations: Transformations performed outside Talend jobs, such as stored procedures or external APIs
  • File-based transformations: Complex transformations in file components without explicit field mappings

For these scenarios, consider using OpenLineage integration with Atlan. OpenLineage captures lineage at job execution time, including custom code transformations and dynamic schemas that static analysis can't detect.

See also​

Need help​

If you can't find the answer you're looking for, contact Atlan support by submitting a request.