<?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>idea Re: Running data warehouse ETL sets in Parallel - Status changed to: Open - New in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idc-p/1879232#M8169</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/133470"&gt;@sriniK&lt;/a&gt;&amp;nbsp;,&amp;nbsp;&lt;/P&gt;&lt;P&gt;In Compose data warehouse projects, we currently don't allow for multiple parallel ETL&amp;nbsp; sets when the same target tables are in a task.&amp;nbsp; &amp;nbsp;This is to prevent duplicate loading of data (if 2 tasks to load TABLEA are running in parallel, Compose could inadvertently load the same business / natural key to a target table).&amp;nbsp; &amp;nbsp;This appears to be the case in your 1st instance.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Typically, customers will put all mappings that load the same target structures into the same ETL set.&amp;nbsp; This ensures parallel loading of the mappings (even across sources) to specific target entities without concern for duplicate data being loaded to the vault.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you confirm that the above scenario is what you are encountering with your scenario (different mappings loading to the same target tables ) ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Jan 2022 23:17:53 GMT</pubDate>
    <dc:creator>TimGarrod</dc:creator>
    <dc:date>2022-01-10T23:17:53Z</dc:date>
    <item>
      <title>Running data warehouse ETL sets in Parallel</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idi-p/1828588</link>
      <description>&lt;P&gt;Compose Data warehouse workflow does not allow running multiple ETL set in parallel. It keeps throwing error -&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;SPAN class="ng-binding"&gt;Task SRC_XREF and task SRC_DRM_FINANCE cannot be run in parallel as at least one of the source entities in their mappings is the same.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class="ng-binding"&gt;Task SRC_DRM_FINANCE and task SRC_XREF cannot be run in parallel as at least one of the source entities in their mappings is the same.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN class="ng-binding"&gt;Task SAPS4HANA_SAPS4_ST_LR_Z3 and task SRC_DRM_FINANCE cannot be run in parallel as at least one of the source entities in their mappings is the same.&lt;/SPAN&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;SPAN class="ng-binding"&gt;Currently we have 15 ETL sets and it takes 5.30 hours to complete the warehouse load. If its possible to run the ETL sets parallelly then&amp;nbsp; the run time can come down considerably.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Aug 2021 19:33:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idi-p/1828588</guid>
      <dc:creator>sriniK</dc:creator>
      <dc:date>2021-08-13T19:33:39Z</dc:date>
    </item>
    <item>
      <title>Re: Running data warehouse ETL sets in Parallel - Status changed to: Open - New</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idc-p/1879232#M8169</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/133470"&gt;@sriniK&lt;/a&gt;&amp;nbsp;,&amp;nbsp;&lt;/P&gt;&lt;P&gt;In Compose data warehouse projects, we currently don't allow for multiple parallel ETL&amp;nbsp; sets when the same target tables are in a task.&amp;nbsp; &amp;nbsp;This is to prevent duplicate loading of data (if 2 tasks to load TABLEA are running in parallel, Compose could inadvertently load the same business / natural key to a target table).&amp;nbsp; &amp;nbsp;This appears to be the case in your 1st instance.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Typically, customers will put all mappings that load the same target structures into the same ETL set.&amp;nbsp; This ensures parallel loading of the mappings (even across sources) to specific target entities without concern for duplicate data being loaded to the vault.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you confirm that the above scenario is what you are encountering with your scenario (different mappings loading to the same target tables ) ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jan 2022 23:17:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idc-p/1879232#M8169</guid>
      <dc:creator>TimGarrod</dc:creator>
      <dc:date>2022-01-10T23:17:53Z</dc:date>
    </item>
    <item>
      <title>Re: Running data warehouse ETL sets in Parallel - Status changed to: Open - Collecting Feedback</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idc-p/1904961#M8953</link>
      <description />
      <pubDate>Mon, 14 Mar 2022 19:43:28 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idc-p/1904961#M8953</guid>
      <dc:creator>TimGarrod</dc:creator>
      <dc:date>2022-03-14T19:43:28Z</dc:date>
    </item>
    <item>
      <title>Re: Running data warehouse ETL sets in Parallel</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idc-p/1917705#M9222</link>
      <description>&lt;P&gt;Compose errors out an ETLSet if another is already running. Would it make sense to keep the scheduled ETLset as pending and run it once the currently running job is over? Workflows allow some of this, but jobs that need to start at fixed times fail if the previous job runs for an extended period.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Apr 2022 21:55:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idc-p/1917705#M9222</guid>
      <dc:creator>ubanerjee</dc:creator>
      <dc:date>2022-04-12T21:55:11Z</dc:date>
    </item>
    <item>
      <title>From now on, please track this idea from the Ideation por...</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idc-p/2113608#M15257</link>
      <description>&lt;P&gt;From now on, please track this idea from the Ideation portal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;A title="Link to new idea" href="https://ideation.qlik.com/app/#/case/274611" target="_blank" rel="noopener"&gt;Link to new idea&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Meghann&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;EM&gt;NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you &lt;STRONG&gt;only&lt;/STRONG&gt; see 1 tab with the login page, please try clicking this link first: &lt;STRONG&gt;&lt;A title="Authenticate me!" href="#" target="_blank" rel="noopener"&gt;Authenticate me!&lt;/A&gt;&lt;/STRONG&gt;&amp;nbsp;t&lt;/EM&gt;&lt;EM&gt;hen try the link above again. Ensure pop-up blocker is off.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Sep 2023 13:13:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idc-p/2113608#M15257</guid>
      <dc:creator>Meghann_MacDonald</dc:creator>
      <dc:date>2023-09-05T13:13:48Z</dc:date>
    </item>
    <item>
      <title>Re: Running data warehouse ETL sets in Parallel - Status changed to: Closed - Archived</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idc-p/2113609#M15258</link>
      <description />
      <pubDate>Tue, 05 Sep 2023 13:13:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Running-data-warehouse-ETL-sets-in-Parallel/idc-p/2113609#M15258</guid>
      <dc:creator>Ideation</dc:creator>
      <dc:date>2023-09-05T13:13:50Z</dc:date>
    </item>
  </channel>
</rss>

