Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
fmrepetto
Partner - Contributor
Partner - Contributor

Compilation Error in tIcebergOutput: "Duplicate local variable schemaArray"

Hi everyone,

I'm encountering a compilation error when trying to use the tIcebergOutput component in a Talend Job (Job Name: Talend_AWS).

The Problem: The Job fails to build/run with a ProcessorException. Upon inspecting the generated Java code, I found that a local variable named schemaArray is being declared multiple times within the same method, causing a "Duplicate local variable" error.

 

Steps taken:

  • I checked the "Code" tab in Talend and confirmed that schemaArray is indeed duplicated in the generated source.

  • I tried to refresh the schema and propagate changes again, but the issue persists.

Has anyone encountered this bug with the Iceberg components? Is there a known workaround?

fmrepetto_0-1776466120142.png

 

Labels (1)
1 Reply
Greg_Taffer
Support
Support

The "Duplicate local variable schemaArray" error in the tIcebergOutput component is a known issue reported in the Qlik Community. It occurs because the auto-generated Java code incorrectly declares the same variable multiple times within a single method scope. 

 

While a permanent fix typically requires a software patch from Talend/Qlik, you can attempt the following workarounds to resolve the compilation failure:


Recommended Workarounds

  • Rename Input/Output Columns: This error sometimes stems from naming conflicts in the schema. Check if any columns in your tIcebergOutput or preceding tMap have identical or very similar names that might trigger redundant code generation.
  • Toggle Schema Mode:
    1. Open the tIcebergOutput component settings and switch the Schema from "Repository" to "Built-in".
    2. Click Edit Schema, manually remove all columns, and then re-add or propagate them again to force a clean code generation.
  • Simplify the Data Flow: If the job contains complex transformations or multiple tIcebergOutput components in the same sub-job, try breaking them into separate sub-jobs using tRunJob. This limits the scope of generated variables in a single Java method.
  • Check for Latest Patches: Similar "Duplicate local variable" bugs in other components (like SQL templates) have historically been fixed in specific monthly Talend patches. Ensure your Talend Studio is updated to the latest available version. 

If these steps do not resolve the issue, it is recommended to follow the official Qlik Support thread (https://community.qlik.com/t5/Talend-Studio/Compilation-Error-in-tIcebergOutput-quot-Duplicate-local...) for a formal bug fix, as this is an internal component code-generation error.