[
https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652809#comment-14652809
]
Andrew Purtell edited comment on HBASE-14122 at 8/3/15 11:56 PM:
-----------------------------------------------------------------
bq. Should all these be refactored to use the new master API for checking
security support?
Let me look into that. Good suggestion.
Would changing how/if exceptions are thrown when using the AccessControlClient
and VisibilityClient be a backwards compatibility concern?
At least with the shell, we can avoid ugly nits by checking security feature
flags in advanced if the API is available. Would also handle the case where the
new master API isn't available. See what the shell does for the new
list_security_capabilities command.
was (Author: apurtell):
bq. Should all these be refactored to use the new master API for checking
security support?
Let me look into that. Good suggestion.
> Client API for determining if server side supports cell level security
> ----------------------------------------------------------------------
>
> Key: HBASE-14122
> URL: https://issues.apache.org/jira/browse/HBASE-14122
> Project: HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Priority: Minor
> Fix For: 2.0.0, 0.98.14, 1.2.0, 1.3.0
>
> Attachments: HBASE-14122-0.98.patch, HBASE-14122-branch-1.patch,
> HBASE-14122.patch, HBASE-14122.patch
>
>
> Add a client API for determining if the server side supports cell level
> security.
> Ask the master, assuming as we do in many other instances that the master and
> regionservers all have a consistent view of site configuration.
> Return {{true}} if all features required for cell level security are present,
> {{false}} otherwise, or throw {{UnsupportedOperationException}} if the master
> does not have support for the RPC call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
