<?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>question Re: SQL loader using PutSQL in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/SQL-loader-using-PutSQL/m-p/112823#M46776</link>
    <description>&lt;P&gt;PutSQL has a mechanism for batching together statements that were split by processors such as SplitText. Set the "&lt;A target="_blank" href="https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutSQL/index.html"&gt;Support Fragmented Transactions&lt;/A&gt;" property to true, and PutSQL will wait until all flow files with the same fragment.identifier have arrived, then it will process them all as a single batch.&lt;/P&gt;&lt;P&gt;There has also been talk of implementing the same improvement for PutSQL as is being done for PutHiveQL (&lt;A target="_blank" href="https://issues.apache.org/jira/browse/NIFI-3031"&gt;NIFI-3031&lt;/A&gt;), to support multiple statements from a single flow file. Please feel free to file a Jira for this if you like. &lt;/P&gt;</description>
    <pubDate>Mon, 21 Nov 2016 21:31:27 GMT</pubDate>
    <dc:creator>mburgess</dc:creator>
    <dc:date>2016-11-21T21:31:27Z</dc:date>
    <item>
      <title>SQL loader using PutSQL</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/SQL-loader-using-PutSQL/m-p/112822#M46775</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;Am trying to build SQL loader using NiFi, the thing which is a bit strange is that I have to split the input file (containing insert statments) to multiple files each containing only one SQL insert, is this the best practice ? why I cant send the whole file to putSQL processor ?&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="9648-screen-shot-2016-11-20-at-90149-pm.png" style="width: 1440px;"&gt;&lt;img src="https://community.cloudera.com/t5/image/serverpage/image-id/23196iF9AB04F411247756/image-size/medium?v=v2&amp;amp;px=400" role="button" title="9648-screen-shot-2016-11-20-at-90149-pm.png" alt="9648-screen-shot-2016-11-20-at-90149-pm.png" /&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 19 Aug 2019 11:12:36 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/SQL-loader-using-PutSQL/m-p/112822#M46775</guid>
      <dc:creator>yahya_najjar</dc:creator>
      <dc:date>2019-08-19T11:12:36Z</dc:date>
    </item>
    <item>
      <title>Re: SQL loader using PutSQL</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/SQL-loader-using-PutSQL/m-p/112823#M46776</link>
      <description>&lt;P&gt;PutSQL has a mechanism for batching together statements that were split by processors such as SplitText. Set the "&lt;A target="_blank" href="https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.standard.PutSQL/index.html"&gt;Support Fragmented Transactions&lt;/A&gt;" property to true, and PutSQL will wait until all flow files with the same fragment.identifier have arrived, then it will process them all as a single batch.&lt;/P&gt;&lt;P&gt;There has also been talk of implementing the same improvement for PutSQL as is being done for PutHiveQL (&lt;A target="_blank" href="https://issues.apache.org/jira/browse/NIFI-3031"&gt;NIFI-3031&lt;/A&gt;), to support multiple statements from a single flow file. Please feel free to file a Jira for this if you like. &lt;/P&gt;</description>
      <pubDate>Mon, 21 Nov 2016 21:31:27 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/SQL-loader-using-PutSQL/m-p/112823#M46776</guid>
      <dc:creator>mburgess</dc:creator>
      <dc:date>2016-11-21T21:31:27Z</dc:date>
    </item>
    <item>
      <title>Re: SQL loader using PutSQL</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/SQL-loader-using-PutSQL/m-p/112824#M46777</link>
      <description>&lt;P&gt;Thanks Matt, very helpful&lt;/P&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;P&gt;is there anyway to use "Load into" instead of SQL insert ?&lt;/P&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 22 Nov 2016 20:19:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/SQL-loader-using-PutSQL/m-p/112824#M46777</guid>
      <dc:creator>yahya_najjar</dc:creator>
      <dc:date>2016-11-22T20:19:49Z</dc:date>
    </item>
    <item>
      <title>Re: SQL loader using PutSQL</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/SQL-loader-using-PutSQL/m-p/112825#M46778</link>
      <description>&lt;P&gt;Yes, PutSQL accepts any SQL statement (except Callable statements like stored procedures) that does not return a result set, so DDL/DML commands such as LOAD INTO or CREATE TABLE, etc. are supported.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2016 02:18:50 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/SQL-loader-using-PutSQL/m-p/112825#M46778</guid>
      <dc:creator>mburgess</dc:creator>
      <dc:date>2016-11-23T02:18:50Z</dc:date>
    </item>
    <item>
      <title>Re: SQL loader using PutSQL</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/SQL-loader-using-PutSQL/m-p/112826#M46779</link>
      <description>&lt;P&gt;big thanks really... &lt;/P&gt;</description>
      <pubDate>Wed, 23 Nov 2016 03:49:59 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/SQL-loader-using-PutSQL/m-p/112826#M46779</guid>
      <dc:creator>yahya_najjar</dc:creator>
      <dc:date>2016-11-23T03:49:59Z</dc:date>
    </item>
  </channel>
</rss>

