<?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: Replicate stored changes: drop table ends up in deleting data in the S3 Bucket - Status changed to: Closed - Archived in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-stored-changes-drop-table-ends-up-in-deleting-data-in/idc-p/2101269#M14511</link>
    <description />
    <pubDate>Wed, 02 Aug 2023 16:19:17 GMT</pubDate>
    <dc:creator>Ideation</dc:creator>
    <dc:date>2023-08-02T16:19:17Z</dc:date>
    <item>
      <title>Replicate stored changes: drop table ends up in deleting data in the S3 Bucket</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-stored-changes-drop-table-ends-up-in-deleting-data-in/idi-p/1758119</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We are replicating Data from our operational System on Db2 Z/Os to a Datalake on S3 for analytic purposes.&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;SPAN&gt;We are replicating the data in a S3 Bucket to store all the data and especially the changes in a datalake.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;SPAN&gt;The replicate task is defined&amp;nbsp; with stored changes and DDL option apply to change table.&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;The apply to chnages is used becasue we want to have the DDL changes automatic available in the Datalake.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;For several reason a change on a table on the source ends up, that the table has to be dropped, and recreated new and the data has to reloaded in this new created table. When this table is replicated the drop table ends up in deleting also all the data in the target. But because we are replicating the data into a datalake, we don't want to delete this history of the data. The idea of datalake is never delete any data.&lt;BR /&gt;Is it possible to change the behavior of the task, that when a table is dropped in the source, this action does not end up with deleting the data in the target?&lt;BR /&gt;&lt;BR /&gt;There is similar behaviour available with apply changes. There it is possible to have the option ignore drop table.&lt;BR /&gt;&lt;BR /&gt;Can such option also be included in stored changes?&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Nov 2020 14:33:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-stored-changes-drop-table-ends-up-in-deleting-data-in/idi-p/1758119</guid>
      <dc:creator>RSch</dc:creator>
      <dc:date>2020-11-25T14:33:18Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate stored changes: drop table ends up in deleting data in the S3 Bucket - Status changed to: Open - Collecting Feedback</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-stored-changes-drop-table-ends-up-in-deleting-data-in/idc-p/1770244#M4626</link>
      <description>&lt;P&gt;Thank you for the feedback.&amp;nbsp; We would like to collect feedback and will consider for a future release.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 23 Dec 2020 14:00:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-stored-changes-drop-table-ends-up-in-deleting-data-in/idc-p/1770244#M4626</guid>
      <dc:creator>Shelley_Brennan</dc:creator>
      <dc:date>2020-12-23T14:00:08Z</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/Replicate-stored-changes-drop-table-ends-up-in-deleting-data-in/idc-p/2101268#M14510</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/274833" 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>Wed, 02 Aug 2023 16:19:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-stored-changes-drop-table-ends-up-in-deleting-data-in/idc-p/2101268#M14510</guid>
      <dc:creator>Meghann_MacDonald</dc:creator>
      <dc:date>2023-08-02T16:19:16Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate stored changes: drop table ends up in deleting data in the S3 Bucket - Status changed to: Closed - Archived</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-stored-changes-drop-table-ends-up-in-deleting-data-in/idc-p/2101269#M14511</link>
      <description />
      <pubDate>Wed, 02 Aug 2023 16:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Replicate-stored-changes-drop-table-ends-up-in-deleting-data-in/idc-p/2101269#M14511</guid>
      <dc:creator>Ideation</dc:creator>
      <dc:date>2023-08-02T16:19:17Z</dc:date>
    </item>
  </channel>
</rss>

