You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Oleg Zhurakousky (JIRA)" <ji...@apache.org> on 2015/10/29 16:35:27 UTC

[jira] [Comment Edited] (NIFI-981) Add support for Hive JDBC / ExecuteSQL

    [ https://issues.apache.org/jira/browse/NIFI-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980630#comment-14980630 ] 

Oleg Zhurakousky edited comment on NIFI-981 at 10/29/15 3:35 PM:
-----------------------------------------------------------------

I doubt there should be any special work for this one other then testing and documenting, since as the issue states its over JDBC. There may be some classpath issues with DBCP controller service and we may need to address those.

[~busbey] While it may be possible with Kite, it doesn't make this issue less valid since at the core of it is ExecuteSQL Processor, which must be able to interact with all JDBC driver. 


was (Author: ozhurakousky):
I doubt there should be any special work for this one other then testing and documenting, since as the issue states its over JDBC. There may be some classpath issues with DBCP controller service and we may need to address those.

> Add support for Hive JDBC / ExecuteSQL
> --------------------------------------
>
>                 Key: NIFI-981
>                 URL: https://issues.apache.org/jira/browse/NIFI-981
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Joseph Witt
>             Fix For: 0.4.0
>
>
> In this mailing list thread from September 2015 "NIFI DBCP connection pool not working for hive" the main thrust of the converstation is to provide proper support for delivering data to hive.  Hive's jdbc driver appears to have dependencies on Hadoop libraries.  We need to be careful/thoughtful about how to best support this so that different versions of Hadoop distros can be supported (potentially in parallel on the same flow).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)