Member since
03-18-2016
3
Posts
6
Kudos Received
0
Solutions
04-05-2016
11:44 AM
2 Kudos
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: https://issues.apache.org/jira/browse/NIFI-981. There are some workarounds described in the following nifi-users email (from the archive): https://mail-archives.apache.org/mod_mbox/nifi-users/201601.mbox/%3C43A01CF2-2CC6-4A01-8836-86B9B3BEA31B@gmail.com%3E
... View more
09-08-2016
07:56 PM
This post is written against Apache NiFi 0.6.1... in that version when you enabled the RPG and it makes a request to the secure instance, it automatically makes an account request for the DN being used by the RPG (mycert.p12). Then someone has to go into the other instance UI and approve that account and give it a role of a NIFI, which behind the scenes updates the authorized_users.xml. This is a bit different in Apache NiFi 1.0.0... there is no more automatic account requests and the authorization model is very different. Refer this blog post for how to setup the authorizations: http://bryanbende.com/development/2016/08/30/apache-nifi-1.0.0-secure-site-to-site
... View more