{"id":23413,"date":"2015-09-08T00:59:55","date_gmt":"2015-09-07T19:29:55","guid":{"rendered":"http:\/\/www.tothenew.com\/blog\/?p=23413"},"modified":"2015-09-17T14:45:06","modified_gmt":"2015-09-17T09:15:06","slug":"talend-passing-values-from-parent-job-to-child-job","status":"publish","type":"post","link":"https:\/\/www.tothenew.com\/blog\/talend-passing-values-from-parent-job-to-child-job\/","title":{"rendered":"Talend : Passing values from Parent Job to Child Job"},"content":{"rendered":"

In the previous post<\/a>, I discussed automating content migration process using Talend. As the power of Talend lies with creating meaningful jobs, it solves a particular business problem. More often than not, one job has to talk to another job.<\/p>\n

Use case:<\/strong><\/p>\n

While working on a migration project, I had a use case where I wanted to pass a value from a Parent Job to a Child Job.<\/p>\n

Problem:<\/strong><\/p>\n

globalMap<\/code>\u00a0is a useful way to pass values, but it can only be used to pass the values within same Job. For Instance, If I have a Job A<\/code> like\u00a0below:<\/p>\n

\"job1\"<\/p>\n

where tJava_1<\/code> is setting a key in globalMap<\/code>,<\/p>\n

[java]globalMap.put("testVal","Test Value 1");[\/java]<\/p>\n

and tJava_2<\/code>\u00a0is trying to retrieve its value.<\/p>\n

[java]System.out.println("testVal in the same job is "+(String)globalMap.get("testVal"));[\/java]<\/p>\n

Its value can be retrieved from the components defined in the same Job but if we try to access those values outside this Job, we’ll get the null value.<\/p>\n

Solution:<\/strong><\/p>\n

The problem can be resolved by utilizing the power of “Context Variables”<\/strong><\/em>. Create a Job 2<\/code>\u00a0like as shown below and define a context variable \"testValue\"<\/em><\/code><\/p>\n

\"job<\/p>\n

Create a Job B<\/code> like as shown below: \u00a0(Job 2<\/code>\u00a0is a tRunJob\u00a0<\/code>component which is calling the above Job)<\/p>\n

\"job2\"<\/p>\n

Here tJava_1<\/code> is setting a key in globalMap<\/code>,<\/p>\n

[java]globalMap.put("testVal","Test Value 1");[\/java]<\/p>\n

To access the above value in Job 2<\/code>\u00a0, define this component’s properties as below. Note the “Context Param\"<\/em><\/code> definition, this is how we can set the value in the context variable and retrieve it in the child job.<\/p>\n

\"final<\/p>\n

tJava_1<\/code> in Child Job can simply retrieve its value :<\/p>\n

[java]System.out.println("testVal in the another job is "+context.testValue);[\/java]<\/p>\n

Hope it helps !!<\/p>\n","protected":false},"excerpt":{"rendered":"

In the previous post, I discussed automating content migration process using Talend. As the power of Talend lies with creating meaningful jobs, it solves a particular business problem. More often than not, one job has to talk to another job. Use case: While working on a migration project, I had a use case where I […]<\/p>\n","protected":false},"author":110,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":55,"footnotes":""},"categories":[1],"tags":[2007,2339,2337,2338,2340,2008],"class_list":["post-23413","post","type-post","status-publish","format-standard","hentry","category-technology","tag-content-migration","tag-context","tag-data-migration","tag-globalmap","tag-passing-values-from-parent-to-child-job","tag-talend"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t