[
https://issues.apache.org/jira/browse/NIFI-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16470775#comment-16470775
]
ASF GitHub Bot commented on NIFI-4637:
--------------------------------------
Github user bbende commented on the issue:
https://github.com/apache/nifi/pull/2518
@MikeThomsen @ijokarumawak I'd say unless there is something in the 1.2
client that is needed to implement the visibility labels, then it might be
safer to just stay on 1.1.2, and hopefully soon we can put out a new NAR for
the 2.0.0 client service, and of course name it "2_x_x" or something. I wish I
had named the current service and NAR "1_1_x" or "1_x_x" from the beginning :(
If we renamed things now then we'd have to rename the NAR and three
services - HBase_1_1_2_ClientService, HBase_1_1_2_RecordLookupService, and
HBase_1_1_2_MapCacheClientService... and then anyone who has an existing flow
with those services will have ghosted components that can no longer find those
class names, and then have to recreate them with the new class to get it
working again.
> Add support for HBase visibility labels to HBase processors and controller
> services
> -----------------------------------------------------------------------------------
>
> Key: NIFI-4637
> URL: https://issues.apache.org/jira/browse/NIFI-4637
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
> Priority: Major
>
> HBase supports visibility labels, but you can't use them from NiFi because
> there is no way to set them. The existing processors and services should be
> upgraded to handle this capability.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
