[
https://issues.apache.org/jira/browse/NIFI-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16452221#comment-16452221
]
ASF GitHub Bot commented on NIFI-4637:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/2518
@MikeThomsen @bbende HBase allows user to set visibility label expression
using labels those are not associated to the user by default. There is a server
side configuration to strict this
`hbase.security.visibility.mutations.checkauths`.
I am not familiar with Accumulo behavior but there was a mention about the
difference between Accumulo and HBase.
> The deletes happen based on pattern matching. If suppose a Cell has
SECRET&TOPSECRET as the visibility expression then any delete coming with the
same expression is matched for, but TOPSECRET&SECRET is also considered to be
same
> A&B<=>B&A
> A|B<=>B|A.
> This is the difference between what Accumulo does in terms of delete
where only the exact match is looked out for.
https://issues.apache.org/jira/browse/HBASE-10885?focusedCommentId=14053522&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-14053522
> 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)
