You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2019/02/25 21:43:00 UTC
[jira] [Commented] (NIFI-5980) HBase List LookupService
[ https://issues.apache.org/jira/browse/NIFI-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16777318#comment-16777318 ]
ASF subversion and git services commented on NIFI-5980:
-------------------------------------------------------
Commit b0a93b473b428f9aa43502411818564703cec59b in nifi's branch refs/heads/master from Mike Thomsen
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b0a93b4 ]
NIFI-5980 Added HBase_1_1_2_ListLookupService.
NIFI-5980 Added HBase_2_ListLookupService.
This closes #3278.
Signed-off-by: Bryan Bende <bb...@apache.org>
> HBase List LookupService
> ------------------------
>
> Key: NIFI-5980
> URL: https://issues.apache.org/jira/browse/NIFI-5980
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
> Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The existing lookup service is designed to return records. This makes it unsuitable for cases where someone wants to pull out a list of keys or values from the returned row and inject that into the record.
> For example, someone looking to add a list of roles to a record for downstream security constraints somewhere might store a lookup in HBase between the data item and its roles. Stored like this:
> <data_item_key>:security:role_admin = 1
> <data_item_key>:security:role_auditor = 1
> When the flow does a lookup on the item, ex. during a reingest event, these fields could be pulled out of HBase and inserted as a List<String> into the record.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)