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

Announcements
Qlik Connect 2026 Agenda Now Available: Explore Sessions
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Tutorial issue: Job compile error

Hi, I searched for this on Google, but the solution was on the old forums, and I also read the old forums were archived instead of migrated here, which I assume is the new version (I think it wasn't a clever decision to dump so many solved issues for a Joomla!-looking forum UI, but that's just my opinion), thus I couldn't read the solution and had to come here to ask again.

 

Long story short, I followed the tutorial step by step: Create input and output components, add a mapper and propagate data from a pre-built CSV to an empty one. All good until I press run and it returns some odd error in code which is likely caused by me skipping some step.

 

0683p000009Lvc7.png

 

The error pops on the output file component, can someone point me in the right direction here?

 

PS: The tag system is really awkward.

Labels (2)
1 Solution

Accepted Solutions
Anonymous
Not applicable
Author

It's hard to diagnose without more information, but usually that error means you have a typo in the parameters for that component (e.g. an extra ")"). Have you enclosed all the parameters that will be referenced by Java in quotes? That's a mistake I've made multiple times 0683p000009MApQ.png

 

Good luck!

 

David

View solution in original post

3 Replies
Anonymous
Not applicable
Author

It's hard to diagnose without more information, but usually that error means you have a typo in the parameters for that component (e.g. an extra ")"). Have you enclosed all the parameters that will be referenced by Java in quotes? That's a mistake I've made multiple times 0683p000009MApQ.png

 

Good luck!

 

David

Anonymous
Not applicable
Author

Thanks for the quick answer.

I checked again and it seems the output file path NEEDS quotes for some reason. I thought it would be parsed properly in the code behind.

Rather counter-intuitive, that was the solution exactly.
cterenzi
Specialist
Specialist

The platform needs to interpret string literals and variables (or both) in component settings, and one or the other needs a delimiter. Talend's design choice hews closely to the Java code it creates, with string literals wrapped with quotes and variables without.