The PR is out: https://github.com/apache/nifi/pull/384
I have a couple of minor changes to make but I think it should be
merged by the end of the day tomorrow.
On Thu, Apr 28, 2016 at 2:50 PM, Mike Harding wrote:
> Hi Matt,
>
> Thanks for the info - do you have an idea when you plan to issue the
Hi Matt,
Thanks for the info - do you have an idea when you plan to issue the PR for
this?
Cheers,
Mike
On Tue, 26 Apr 2016 at 14:47, Matt Burgess wrote:
> Hive doesn't work with ExecuteSQL as its JDBC driver does not support
> all the JDBC API calls made by ExecuteSQL / PutSQL. However I am
Hive doesn't work with ExecuteSQL as its JDBC driver does not support
all the JDBC API calls made by ExecuteSQL / PutSQL. However I am
working on a Hive NAR to include ExecuteHiveQL and PutHiveQL
processors (https://issues.apache.org/jira/browse/NIFI-981), there is
a prototype pull request on GitH
Hi Mike,
I never tried but using the JDBC client you should be able to query your
Hive table using ExecuteSQL processor.
Hope that helps,
Pierre
2016-04-26 13:53 GMT+02:00 Mike Harding :
> Hi All,
>
> I have a requirement to access a lookup Hive table to translate a code
> number in a FlowFile
Hi All,
I have a requirement to access a lookup Hive table to translate a code
number in a FlowFile to a readable name. I'm just unsure how trivial it is
to connect to the db from an ExecuteScript processor?
Nifi and the hiveserver2 sit on the same node so I'm wondering if its
possible to use Hiv
