<?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: ExecuteSQL - Hive Error in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/ExecuteSQL-Hive-Error/m-p/156699#M24438</link>
    <description>&lt;P&gt;Even with the standalone JAR, ExecuteSQL will not work with Hive due to the Hive JDBC driver not implementing some of the JDBC API calls made by ExecuteSQL. There is a Jira case to add Hive support: &lt;A href="https://issues.apache.org/jira/browse/NIFI-981" target="_blank"&gt;https://issues.apache.org/jira/browse/NIFI-981&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;There are some workarounds described in the following nifi-users email (from the archive): &lt;A target="_blank" href="https://mail-archives.apache.org/mod_mbox/nifi-users/201601.mbox/%3C43A01CF2-2CC6-4A01-8836-86B9B3BEA31B@gmail.com%3E"&gt;https://mail-archives.apache.org/mod_mbox/nifi-users/201601.mbox/%3C43A01CF2-2CC6-4A01-8836-86B9B3BEA31B@gmail.com%3E&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 05 Apr 2016 18:44:25 GMT</pubDate>
    <dc:creator>mburgess</dc:creator>
    <dc:date>2016-04-05T18:44:25Z</dc:date>
    <item>
      <title>ExecuteSQL - Hive Error</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/ExecuteSQL-Hive-Error/m-p/156698#M24437</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have a simple NIFI Flow to read results from HIVE tables,please find the image below.&lt;/P&gt;&lt;P&gt;ExecuteSQL throws exception when tried to issue simple HIVEQL like 'show tables' or 'select * from &amp;lt;tablename&amp;gt;.&lt;/P&gt;&lt;P&gt;Database Connection Pooling Service is set with HIVE credentials and its status is "Enabled".&lt;/P&gt;&lt;P&gt;'hive-jdbc-x.x.x-standalone.jar' is used for Database DriverJar Url in configuration of DCPS.&lt;/P&gt;&lt;P&gt;'hadoop-common-x.x.x.jar' is set as part of system CLASSPATH.&lt;/P&gt;&lt;P&gt;Can any point out whats missing to make this simple flow workable.&lt;/P&gt;&lt;P&gt;NIFI 0.6.0 is used.&lt;/P&gt;&lt;P&gt;Thanks in adv,&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Time&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.cloudera.com/legacyfs/online/attachments/3208-hivejdbc.png"&gt;hivejdbc.png&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Apr 2016 17:35:30 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/ExecuteSQL-Hive-Error/m-p/156698#M24437</guid>
      <dc:creator>timestationapp</dc:creator>
      <dc:date>2016-04-05T17:35:30Z</dc:date>
    </item>
    <item>
      <title>Re: ExecuteSQL - Hive Error</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/ExecuteSQL-Hive-Error/m-p/156699#M24438</link>
      <description>&lt;P&gt;Even with the standalone JAR, ExecuteSQL will not work with Hive due to the Hive JDBC driver not implementing some of the JDBC API calls made by ExecuteSQL. There is a Jira case to add Hive support: &lt;A href="https://issues.apache.org/jira/browse/NIFI-981" target="_blank"&gt;https://issues.apache.org/jira/browse/NIFI-981&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;There are some workarounds described in the following nifi-users email (from the archive): &lt;A target="_blank" href="https://mail-archives.apache.org/mod_mbox/nifi-users/201601.mbox/%3C43A01CF2-2CC6-4A01-8836-86B9B3BEA31B@gmail.com%3E"&gt;https://mail-archives.apache.org/mod_mbox/nifi-users/201601.mbox/%3C43A01CF2-2CC6-4A01-8836-86B9B3BEA31B@gmail.com%3E&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Apr 2016 18:44:25 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/ExecuteSQL-Hive-Error/m-p/156699#M24438</guid>
      <dc:creator>mburgess</dc:creator>
      <dc:date>2016-04-05T18:44:25Z</dc:date>
    </item>
  </channel>
</rss>

