[
https://issues.apache.org/jira/browse/NIFI-817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14951320#comment-14951320
]
Nick Dimiduk commented on NIFI-817:
-----------------------------------
(1) yeah, reps are a mess. Maybe the hbase-client-shaded jars we're shipping in
1.1+ will help?
(2) yep, see
https://github.com/apache/hbase/blob/master/hbase-client/src/main/java/org/apache/hadoop/hbase/filter/ParseFilter.java
(3) I hate seeing code like that. Sorry, I don't know anything about hoe nifi
manages class paths. Better to put the equivalent of /etc/hbase/conf and
/etc/hadoop/conf on the process classpath and just use
HBaseConfiguration.create(). It'll do the right thing. Have a look at the
output of {{bin/hbase classpath}} for some ideas, maybe that'll help.
Also, do you have a log4j.properties file on the classpath? If you do, the zk
connection stuff will tell you more. Make sure it's talking to your quorum and
not localhost. If it's localhost, probably it's not finding hbase-site.xml.
Yeah, "stuck" I think it'll retry 35 times with exponential back off over a
period of about 10 minutes. Yeah, basically stuck.
> Create Processors to interact with HBase
> ----------------------------------------
>
> Key: NIFI-817
> URL: https://issues.apache.org/jira/browse/NIFI-817
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Bryan Bende
> Fix For: 0.4.0
>
> Attachments:
> 0001-NIFI-817-Initial-implementation-of-HBase-processors-2.patch,
> 0001-NIFI-817-Initial-implementation-of-HBase-processors.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
