<?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: HIVE insert/update/delete in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HIVE-insert-update-delete/m-p/228567#M61038</link>
    <description>&lt;P&gt;In Nifi, you can use the PutHiveStreaming processor, and it is designed to commit transactions in batch, which is configurable.&lt;/P&gt;&lt;P&gt;&lt;A href="https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.2.0/org.apache.nifi.processors.hive.PutHiveStreaming/index.html" target="_blank"&gt;https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.2.0/org.apache.nifi.processors.hive.PutHiveStreaming/index.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I think risky is not the correct term for using an ACID table, but careful may be better; that is, with careful design and configuration, you can avoid locking issues. Be sure to review the Hive documentation on this:&lt;/P&gt;&lt;P&gt;&lt;A href="https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions" target="_blank"&gt;https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 09 Jun 2017 00:28:30 GMT</pubDate>
    <dc:creator>bhagan</dc:creator>
    <dc:date>2017-06-09T00:28:30Z</dc:date>
    <item>
      <title>HIVE insert/update/delete</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HIVE-insert-update-delete/m-p/228566#M61037</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I tried HIVE insert/update/delete operations, I see that it launches a tez job and bit slow. I have a couple of questions -&lt;/P&gt;&lt;P&gt;1. when we use hive streaming processors (in nifi, streamsets) does it insert record by record? I believe no. just to confirm.&lt;/P&gt;&lt;P&gt;2. it seems bit risky to design an acid hive table, is there an approach where it can be used (such as IOT ) safely without having locking/concurrency issues etc.&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Avijeet&lt;/P&gt;</description>
      <pubDate>Fri, 12 May 2017 12:51:28 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HIVE-insert-update-delete/m-p/228566#M61037</guid>
      <dc:creator>avijeetd</dc:creator>
      <dc:date>2017-05-12T12:51:28Z</dc:date>
    </item>
    <item>
      <title>Re: HIVE insert/update/delete</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/HIVE-insert-update-delete/m-p/228567#M61038</link>
      <description>&lt;P&gt;In Nifi, you can use the PutHiveStreaming processor, and it is designed to commit transactions in batch, which is configurable.&lt;/P&gt;&lt;P&gt;&lt;A href="https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.2.0/org.apache.nifi.processors.hive.PutHiveStreaming/index.html" target="_blank"&gt;https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-hive-nar/1.2.0/org.apache.nifi.processors.hive.PutHiveStreaming/index.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;I think risky is not the correct term for using an ACID table, but careful may be better; that is, with careful design and configuration, you can avoid locking issues. Be sure to review the Hive documentation on this:&lt;/P&gt;&lt;P&gt;&lt;A href="https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions" target="_blank"&gt;https://cwiki.apache.org/confluence/display/Hive/Hive+Transactions&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 09 Jun 2017 00:28:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/HIVE-insert-update-delete/m-p/228567#M61038</guid>
      <dc:creator>bhagan</dc:creator>
      <dc:date>2017-06-09T00:28:30Z</dc:date>
    </item>
  </channel>
</rss>

