Qlik Talend Data Catalog: How to get Lineage from Qlik Talend Studio Jobs that use tJava/tJavaRow/tDBRow components

[chris_khalife]

By default, Qlik Talend Data Catalog will not be able to trace the lineage of Qlik Talend Studio jobs that use dynamic components such as tDBJava. To extract lineage correctly, there are multiple steps that need to be followed. Below is an example where the JavaRow lineage fails to show because Talend Data Catalog is not able to parse the lineage of tJavaRow and instead creates duplicate columns, unintentionally splitting the lineage for each column:

Requirements

The following versions are required to trace lineage for complex Qlik Talend Studio components:

• Qlik Talend Studio R2025-04
• Qlik Talend Data Catalog 2026-02-10

Steps

1. In Qlik Talend Studio, confirm you have a complex component that will require advanced lineage tracing. In the example job below (MySqlToMySql_tJava) the tJavaRow component is included.
   
   
   
   
2. In Qlik Talend Studio, navigate to Project Settings (A) > Job Settings (B) and verify that Disable Lineage (C)is not checked for Qlik Cloud:
   

   

    
   If this setting is not available to you in Studio due to using an on-prem or local connection, then in the Qlik Talend Studio directory, edit the .ini file:
   
   -Dtalend.lineage.enabled=true 
   
   Example: Talend-Studio-win-x86_64.ini
   

   -vm
   C:\Talend\Studio-QTC\zulu17.48....
   -vmargs
   -Xms512m
   -Xmx1536m
   -Dfile.encoding=UTF-8
   -Dtalend.lineage.enabled=true
   -XX:+UseG1GC
   -XX:+UseStringDeduplication
   -XX:MaxMetaspaceSize=512m
   --add-modules=ALL-SYSTEM

   
   
3. In Qlik Talend Studio, for the complex components (example: tJavaRow) open the component view and switch from Basic settings to Documentation.
   
   In Documentation, add all columns where lineage should be traced between the flags *** lineage start *** and *** lineage end ***.
   
   Below is an example for five columns:
   
   

   

    
   
   
   
   
   
   To clarify for the screenshot above, not all the code should be placed in Documentation. Only the necessary code to track the lineage of each column should be added, in this case, showing output_row.ColumnName = input_Row.ColumnName.
   
   
4. In the Run tab for Qlik Talend Studio, navigate to Advanced settings (A) > JVM Settings (B).
   
   Add the following flag (C) to generate the necessary JSON files for Talend Data Catalog:
   
   -Druntime.lineage.outputpath=<outputPath>(Example: -Druntime.lineage.outputpath=C:\Talend\TalendStudio\Lineage
   
   
   
5. Run the Qlik Talend Studio job and confirm the JSON is generated in the specified output path:
   
   
   
   
6. Create a new model in Qlik Talend Data Catalog using the Talend Data Integration bridge.
   
   Under the Miscellaneous parameters, include the following flags:
   
   
   1. -runtime.lineage: This should specify where the lineage folder resides. Note that the Project Path must be properly defined for this to work (example: CHRIS_PROJECT\MySQLToMySQL_tJava\01
   2. -runtime.lineage.components: Specifies the list of transformation components that will require the external runtime lineage log by providing a semicolon-separated list of <components type> themselves, optionally prefixed by their job name <job name>.<component type> 
      
      
      
7. Run the import for the model.
   
   Be sure to also create a Qlik Talend Data Catalog for your input and output components to get the full lineage. In the example being used, two SQL models were created for tDBInput and tDBOutput. Once all models are imported, be sure to add the database models as connections to your Qlik Talend model:
   
   
   
   
8. Open the Lineage for the specific job in the model. Here you will see all the lineage is included:
   
   
   

Environment

• Qlik Talend Studio
• Qlik Talend Data Integration