<?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: Developing Jobs with Subjob vs Joblet in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Developing-Jobs-with-Subjob-vs-Joblet/m-p/2220857#M15091</link>
    <description>Hi,&lt;BR /&gt;Joblets are used for repeatable pieces of code/processing that are called within individual mappings.&lt;BR /&gt;&lt;BR /&gt;Subjobs are used to encompass processing/flows that involve multiple mappings. So there is difference.&lt;BR /&gt;HTH</description>
    <pubDate>Sat, 16 Apr 2011 00:37:13 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2011-04-16T00:37:13Z</dc:date>
    <item>
      <title>Developing Jobs with Subjob vs Joblet</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Developing-Jobs-with-Subjob-vs-Joblet/m-p/2220856#M15090</link>
      <description>In designing jobs in Talend, what is the difference between using a subjob vs a joblet? One benefit I see in joblets is that you don't have to specify the "type" of input/output (Excel vs. file delimited vs. XML). Are there any other key differences?</description>
      <pubDate>Sat, 16 Nov 2024 12:58:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Developing-Jobs-with-Subjob-vs-Joblet/m-p/2220856#M15090</guid>
      <dc:creator>_AnonymousUser</dc:creator>
      <dc:date>2024-11-16T12:58:43Z</dc:date>
    </item>
    <item>
      <title>Re: Developing Jobs with Subjob vs Joblet</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Developing-Jobs-with-Subjob-vs-Joblet/m-p/2220857#M15091</link>
      <description>Hi,&lt;BR /&gt;Joblets are used for repeatable pieces of code/processing that are called within individual mappings.&lt;BR /&gt;&lt;BR /&gt;Subjobs are used to encompass processing/flows that involve multiple mappings. So there is difference.&lt;BR /&gt;HTH</description>
      <pubDate>Sat, 16 Apr 2011 00:37:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Developing-Jobs-with-Subjob-vs-Joblet/m-p/2220857#M15091</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2011-04-16T00:37:13Z</dc:date>
    </item>
    <item>
      <title>Re: Developing Jobs with Subjob vs Joblet</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Developing-Jobs-with-Subjob-vs-Joblet/m-p/2220858#M15092</link>
      <description>the word 'subjob' is normally used to denote a set of nested components (indicated by the blue box)-- a joblet can be a part of a subjob, an external job called by a tRunJob is not. I am assuming that you mean the difference between a joblet and an external job called with tRunJob. 
&lt;BR /&gt; 
&lt;BR /&gt;The major difference is in how the code is generated. as a rule of thumb, you can think of executing a joblet as adding the components directly in the job father- while a job called by a tRunJob is executed by calling an external jar.</description>
      <pubDate>Mon, 18 Apr 2011 15:39:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Developing-Jobs-with-Subjob-vs-Joblet/m-p/2220858#M15092</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2011-04-18T15:39:18Z</dc:date>
    </item>
  </channel>
</rss>

