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: 
Abdelrhman_Mohamed
Partner - Contributor
Partner - Contributor

Modifying context parameters for specific tasks in Talend Administration Center

Are there any differences between modifying context parameters for a Normal or Artifact tasks in Job Conductor in TAC?
In another words, does any one of them hold an advantage in terms of modifying context parameters?

Labels (2)
1 Solution

Accepted Solutions
Mohammed_Messaoudi

Helllo,

A normal task from nexus repository is like when you download the Job zip file in local and then add it as an archive file into your TAC, which doesn't maintain the links/references between Talend Administration Center and Nexus (one time download).


An artifact task from nexus repository will check the Job references between Talend Administration Center and Nexus at execution time and then download the newest job.

When you select an artifact task, the Job has a reference to Nexus. For example, you select the latest version of say, 0.3, of the Job in Version while adding a task. Then you change the Job in Studio and publish it with a new version of say, 0.4. The artifact task downloads the latest version, that is 0.4, before running it in the JobServer, since it has a reference to the Nexus. However, a similar Job selected through the normal task (select artifact from Nexus repository), still uses 0.3, because it don't have a reference to Nexus.


 

View solution in original post

3 Replies
Mohammed_Messaoudi

Helllo,

A normal task from nexus repository is like when you download the Job zip file in local and then add it as an archive file into your TAC, which doesn't maintain the links/references between Talend Administration Center and Nexus (one time download).


An artifact task from nexus repository will check the Job references between Talend Administration Center and Nexus at execution time and then download the newest job.

When you select an artifact task, the Job has a reference to Nexus. For example, you select the latest version of say, 0.3, of the Job in Version while adding a task. Then you change the Job in Studio and publish it with a new version of say, 0.4. The artifact task downloads the latest version, that is 0.4, before running it in the JobServer, since it has a reference to the Nexus. However, a similar Job selected through the normal task (select artifact from Nexus repository), still uses 0.3, because it don't have a reference to Nexus.


 

Abdelrhman_Mohamed
Partner - Contributor
Partner - Contributor
Author

Hello,  

Thanks for the quick support.  

I appreciate the clarification on the difference between the Normal and Artifact Task. However, does this mean that if I change the context parameters in the Artifact Task, they will change again when I publish a new version of the Job, or will they stay the same regardless of how many versions I publish for the same Job?  

For the Normal Task, from what I understand, it’s a one-time upload to TAC, so the context parameters shouldn’t change if I add a new version of the same Job, correct?  

Mohammed_Messaoudi

for an Artifact task, the context values are tied to the task configuration, not automatically replaced every time you publish a new job version