[
https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653886#comment-14653886
]
Andrew Purtell commented on HBASE-14122:
----------------------------------------
bq. You seem to be using 'UnsupportedOperationException' for backward
compatibility, depending on it being thrown by the RPC facility if the method
can not be located on the server side
Strictly speaking, I don't depend on it . If it's not supported on the server,
the invocation will get back an IOE because the server couldn't process the
call. The new API and the AccessControlClient and VisibilityClient utility
methods will let that IOE out to the caller. However I do try to do something
nice in the shell so we can print a clean message instead of a stack trace.
This relies on string matching given how remote exceptions work. I think that's
fine for the shell but too brittle to do in the API. What do you think?
> 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)
