hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry He (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14122) Client API for determining if server side supports cell level security
Date Tue, 04 Aug 2015 05:09:05 GMT

    [ https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653069#comment-14653069

Jerry He commented on HBASE-14122:

Another comment.
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?
Have not seen such example before in the HBase code.   This is probably ok.   Usually we explicitly
construct the 'UnsupportedOperationException' at user code level?
It works fine?  The exception will be correctly propagated to the client?

> 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,
> 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

View raw message