Duplicate local variable i

[Anonymous]

Hello there,

I'm having a problem with my talend OSDI Job. I use multiple imports and export with one tMap, like in picture 1.

Now, when i get an error because of a duplicate local variable in a for-query, like in picture 2. Talend offers me to change the name of the variable from"i" to "i1", like in picture 3, but that doesnt work. I got the except same error again. I didn't made anything custom. This was all automaticly made by talend.

Hope you can help me,

Bastian

picture 1picture 2picture 3

[Anonymous]

Hi
I think it is a design issue, you need a tUnite to merge all data that come from different files during the iteration before doing join. eg:
tfileList--iterate--tFileInputXML--tUnite--lookup---tMap....

Can you test and let me know if it works?

Regards
Shong

[Anonymous]

Hi shong,

there ist a Problem. I can't use tUnite, because all the imports are connected to another export, with different amounts of rows. 

The structure is:

Projekt(1)

> Funktionstraeger (0 to n)

> etc (0 to n)

If i would use tUnite there would be a Problem with importing to the right direction.

Regards Bastian

[Anonymous]

Hello,

a short update: I changed the job in subjobs, but now i get the same error again. The job got only one input, like in Picture 1.

Every subjob should work on his own, bute i get the same error on every jobexecute. Maybe its another problem?

Greetings Bastian

Picture 1

[Anonymous]

Hi
Are you using custom component? Which component do you use for 'Projekt'?

Regards
Shong

[Anonymous]

Hello shong,

yes i am using custom components made by a partner company of the company i am working for. 

The same thing, where the error happens, worked in multiple other jobs. Only here i get this error.

Greetings Bastian

[Anonymous · Accepted solution]

In this job, you have iterations, and have several outputs from tMap to custom components, can you check other jobs which are working to see if they have the same part of design, I am wondering whether the issue comes from the custom component.

Regards
Shong

[Anonymous]

Hello,
I already contacted the developer oft he components and they are looking for a fix.
The problem is made by them in the new version oft he components.
Greetings Bastian