[
https://issues.apache.org/jira/browse/HBASE-12373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14218669#comment-14218669
]
Jerry He commented on HBASE-12373:
----------------------------------
Hi, [~apurtell]
Thanks for the comment. All are thoughtful points!
While I was working on this JIRA and looking into the code, there were some
observations that match your comment.
There seems to be somewhere we explicitly imply that there is only one labels
region (and we prevent the splitting of this region). I wonder why? I will
look again and get the code piece.
For most of the security related client tasks, we normally send protobuf
request to the security end points (AccessController and VisibilityController)
to execute and return results.
My guess was that this was probably because 'security' is a 'plugin' and not in
the core server code yet.
And you mentioned another reason in your comment: the 'service provider' on the
server side (e.g. visibility label service provider) dictates the policy and
result ultimately.
Adding an optional parameter supplying a regex looks like a 'must'. I will
look into it.
> Provide a command to list visibility labels
> -------------------------------------------
>
> Key: HBASE-12373
> URL: https://issues.apache.org/jira/browse/HBASE-12373
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 0.98.7, 0.99.1
> Reporter: Jerry He
> Assignee: Jerry He
> Priority: Minor
> Fix For: 0.98.9, 0.99.2
>
> Attachments: HBASE-12373-master-v2.patch,
> HBASE-12373-master-v3.patch, HBASE-12373-master.patch
>
>
> A command to list visibility labels that are in place would be handy.
> This is also in line with many of the other hbase list commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
