<?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 Replicate for datalake in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Replicate-for-datalake/m-p/1692645#M134</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Is there any option, to maintain the historical data from source to datalake using attunity replicate. I know that Qlik also has attunity compose for datalake. But instead of taking another tool, is there any option to maintain historical data in replicate tool itself.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Instead of creating the change tables, the main tables itself should maintain the history of the record for past some days , say example : past 7 days data.&lt;/P&gt;&lt;P&gt;If so please let me know. Appreciate your help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Deepthi.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Apr 2020 12:21:13 GMT</pubDate>
    <dc:creator>suvbin</dc:creator>
    <dc:date>2020-04-10T12:21:13Z</dc:date>
    <item>
      <title>Replicate for datalake</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Replicate-for-datalake/m-p/1692645#M134</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Is there any option, to maintain the historical data from source to datalake using attunity replicate. I know that Qlik also has attunity compose for datalake. But instead of taking another tool, is there any option to maintain historical data in replicate tool itself.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Instead of creating the change tables, the main tables itself should maintain the history of the record for past some days , say example : past 7 days data.&lt;/P&gt;&lt;P&gt;If so please let me know. Appreciate your help.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Deepthi.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Apr 2020 12:21:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Replicate-for-datalake/m-p/1692645#M134</guid>
      <dc:creator>suvbin</dc:creator>
      <dc:date>2020-04-10T12:21:13Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate for datalake</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Replicate-for-datalake/m-p/1692657#M136</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Replicate is designed for capturing changed records from the source and delivering it to the target.&lt;/P&gt;&lt;P&gt;As you said your self, we can deliver the data in change tables or in an audit stream.&lt;/P&gt;&lt;P&gt;But to organize it in into historical consumable records, you need ETL post processing.&lt;/P&gt;&lt;P&gt;This can be automated with Compose or even home grown scripting.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Apr 2020 13:29:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Replicate-for-datalake/m-p/1692657#M136</guid>
      <dc:creator>Ola_Mayer</dc:creator>
      <dc:date>2020-04-10T13:29:01Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate for datalake</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Replicate-for-datalake/m-p/1692663#M137</link>
      <description>&lt;P&gt;Thank you for the response.&amp;nbsp;&lt;/P&gt;&lt;P&gt;The scripting can we write in replicate for maintain historical data. If so where it can be written in replicate.&lt;/P&gt;&lt;P&gt;Can you please be more detail on this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Apr 2020 14:25:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Replicate-for-datalake/m-p/1692663#M137</guid>
      <dc:creator>suvbin</dc:creator>
      <dc:date>2020-04-10T14:25:12Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate for datalake</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Replicate-for-datalake/m-p/1692702#M138</link>
      <description>&lt;P&gt;Replicate is designed to deliver data from point to point with maximum speed and minimum impact on the sources.&lt;/P&gt;&lt;P&gt;Unless transformation can happen in-line, the scripting should be written outside of Replicate.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Apr 2020 18:41:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Replicate-for-datalake/m-p/1692702#M138</guid>
      <dc:creator>Ola_Mayer</dc:creator>
      <dc:date>2020-04-10T18:41:58Z</dc:date>
    </item>
    <item>
      <title>Re: Replicate for datalake</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Replicate-for-datalake/m-p/1693323#M143</link>
      <description>&lt;P&gt;I do not see any feature to store&amp;nbsp;&lt;SPAN&gt;&amp;nbsp;history of the record for ADLS.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;This would be consider as Store change tables.&lt;/P&gt;</description>
      <pubDate>Tue, 14 Apr 2020 14:27:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Replicate-for-datalake/m-p/1693323#M143</guid>
      <dc:creator>stevenguyen</dc:creator>
      <dc:date>2020-04-14T14:27:49Z</dc:date>
    </item>
  </channel>
</rss>

