[
https://issues.apache.org/jira/browse/NIFI-5980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Bende resolved NIFI-5980.
-------------------------------
Resolution: Fixed
Fix Version/s: 1.10.0
> 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
> Fix For: 1.10.0
>
> 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)
