[
https://issues.apache.org/jira/browse/NIFI-4346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194984#comment-16194984
]
ASF GitHub Bot commented on NIFI-4346:
--------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/2125
@MikeThomsen Thanks for the updates...
While I was testing this I started thinking that maybe the lookup service
should be using an HBaseClientService, rather then extending it.
My thinking is that, if you wanted to have several lookup services, they
shouldn't all have to create their own set of connections, they can all just
use one client service.
I took a shot at making these changes and put them in a branch here:
https://github.com/bbende/nifi/commits/NIFI-4346
Since the scan is going through the client service now, I had to make a
slight change to the way the column families and qualifiers are specified. I
made it follow the pattern from the 'Columns' property in GetHBase.
Let me know what you think about these changes. If you are on-board with
this approach then I can go ahead and commit all of this, keeping your original
commit as the starting point of course.
> Add a lookup service that uses HBase
> ------------------------------------
>
> Key: NIFI-4346
> URL: https://issues.apache.org/jira/browse/NIFI-4346
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mike Thomsen
> Priority: Minor
>
> A LookupService based on HBase should be able to handle at least two
> scenarios:
> 1. Pull a single cell and return it as a string.
> 2. Pull multiple cells and return them as a Record that can be merged into
> another record.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
