<?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 Split source table based on record count for processing big Oracle tables in Talend Studio</title>
    <link>https://community.qlik.com/t5/Talend-Studio/Split-source-table-based-on-record-count-for-processing-big/m-p/2228554#M19785</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;I have a very massive&amp;nbsp;table whose record count will be more than 10 billion.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;1. I wanted to read the data from input table for first 2 billion, process it and write to output table.&lt;/P&gt; 
&lt;P&gt;Then fetch next 2 billion and do the same process and write to output table.&lt;/P&gt; 
&lt;P&gt;how could I design my job so that it loops to fetch 2 billion at a time. This design should also consider restartability at record level if it errors(checkpoint at each row if this is the best approach).&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;2. Can I run as a seperate process each 2 billion records?&lt;/P&gt; 
&lt;P&gt;Thanks&lt;/P&gt;</description>
    <pubDate>Tue, 06 Nov 2018 15:55:07 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2018-11-06T15:55:07Z</dc:date>
    <item>
      <title>Split source table based on record count for processing big Oracle tables</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Split-source-table-based-on-record-count-for-processing-big/m-p/2228554#M19785</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;I have a very massive&amp;nbsp;table whose record count will be more than 10 billion.&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;1. I wanted to read the data from input table for first 2 billion, process it and write to output table.&lt;/P&gt; 
&lt;P&gt;Then fetch next 2 billion and do the same process and write to output table.&lt;/P&gt; 
&lt;P&gt;how could I design my job so that it loops to fetch 2 billion at a time. This design should also consider restartability at record level if it errors(checkpoint at each row if this is the best approach).&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;&amp;nbsp;&lt;/P&gt; 
&lt;P&gt;2. Can I run as a seperate process each 2 billion records?&lt;/P&gt; 
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Tue, 06 Nov 2018 15:55:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Split-source-table-based-on-record-count-for-processing-big/m-p/2228554#M19785</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-11-06T15:55:07Z</dc:date>
    </item>
    <item>
      <title>Re: Split source table based on record count for processing big Oracle tables</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Split-source-table-based-on-record-count-for-processing-big/m-p/2228555#M19786</link>
      <description>You may also read the table at once and redirect the content to delimited files with the desired number of records for each. 
&lt;BR /&gt;On a separate process, you can start to read the 1rst file as soon as the 2nd one is created and so on. 
&lt;BR /&gt;This way you can start to process the result before the query is finished and restart on the file of your choice in case of. 
&lt;BR /&gt;Restartability at record level is an other story and I'm not sure checkpoint for each row is an option with such a large volume. 
&lt;BR /&gt;Paralelization for insert should be possible in append mode to avoid locks on table (as far as I remember) but you probably need to limit the number of parallel processes. 
&lt;BR /&gt;That's just some ideas. Let us know the rest of the story. Good luck.</description>
      <pubDate>Tue, 06 Nov 2018 22:42:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Split-source-table-based-on-record-count-for-processing-big/m-p/2228555#M19786</guid>
      <dc:creator>TRF</dc:creator>
      <dc:date>2018-11-06T22:42:53Z</dc:date>
    </item>
    <item>
      <title>Re: Split source table based on record count for processing big Oracle tables</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Split-source-table-based-on-record-count-for-processing-big/m-p/2228556#M19787</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the suggestion.&lt;/P&gt;&lt;P&gt;I &amp;nbsp;have used table to store&amp;nbsp;restart and record&amp;nbsp;split details which will be input to the child job.&lt;/P&gt;&lt;P&gt;And I have created parallel flow creating multiple job reading from the same table.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Nov 2018 11:59:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Split-source-table-based-on-record-count-for-processing-big/m-p/2228556#M19787</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-11-08T11:59:21Z</dc:date>
    </item>
    <item>
      <title>Re: Split source table based on record count for processing big Oracle tables</title>
      <link>https://community.qlik.com/t5/Talend-Studio/Split-source-table-based-on-record-count-for-processing-big/m-p/2228557#M19788</link>
      <description>&lt;P&gt;Hi TRF,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Like tCheckpoint customised component, is there any customised component that support parallel execution as well as restartability at job-level?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Revathy.&lt;/P&gt;</description>
      <pubDate>Sat, 10 Nov 2018 13:06:15 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Talend-Studio/Split-source-table-based-on-record-count-for-processing-big/m-p/2228557#M19788</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2018-11-10T13:06:15Z</dc:date>
    </item>
  </channel>
</rss>

