<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to get a global variable value from a child job? in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/How-to-get-a-global-variable-value-from-a-child-job/m-p/2221542#M15506</link>
    <description>&lt;P&gt;to pass data from a child job back to the parent you should use the tBufferOutput component in the child job. A common pattern is to use a tFixedFlowInput--&amp;gt;tBufferOutput combination as the last two components in the job to pass context or globalMap variables back to the parent.&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;the "copy child job schema" button becomes available in the parent job's tRunJob component once you have the tBufferOutput in the child job. This should copy the schema of the child job tBufferOutput to the tRunJob component. You can then connect it to other components in the parent job using the row connector.&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;One thing to keep in mind is that you should attempt to limit the amount of data you pass from child to parent. If you find you need to pass a large amount, consider refactoring your child job into a joblet.&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 02 Nov 2018 18:28:00 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2018-11-02T18:28:00Z</dc:date>
    <item>
      <title>How to get a global variable value from a child job?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/How-to-get-a-global-variable-value-from-a-child-job/m-p/2221541#M15505</link>
      <description>&lt;P&gt;I have a main job---&amp;gt;calling a child job---&amp;gt; inside a child job calling another child job.&amp;nbsp; 3 layers of it.&lt;/P&gt;
&lt;P&gt;How do I get the 3rd child job global variable information passed to the main job?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Nov 2018 17:28:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/How-to-get-a-global-variable-value-from-a-child-job/m-p/2221541#M15505</guid>
      <dc:creator>rp2018</dc:creator>
      <dc:date>2018-11-02T17:28:24Z</dc:date>
    </item>
    <item>
      <title>Re: How to get a global variable value from a child job?</title>
      <link>https://community.qlik.com/t5/Talend-Studio/How-to-get-a-global-variable-value-from-a-child-job/m-p/2221542#M15506</link>
      <description>&lt;P&gt;to pass data from a child job back to the parent you should use the tBufferOutput component in the child job. A common pattern is to use a tFixedFlowInput--&amp;gt;tBufferOutput combination as the last two components in the job to pass context or globalMap variables back to the parent.&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;the "copy child job schema" button becomes available in the parent job's tRunJob component once you have the tBufferOutput in the child job. This should copy the schema of the child job tBufferOutput to the tRunJob component. You can then connect it to other components in the parent job using the row connector.&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;One thing to keep in mind is that you should attempt to limit the amount of data you pass from child to parent. If you find you need to pass a large amount, consider refactoring your child job into a joblet.&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 02 Nov 2018 18:28:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/How-to-get-a-global-variable-value-from-a-child-job/m-p/2221542#M15506</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-11-02T18:28:00Z</dc:date>
    </item>
  </channel>
</rss>

