[ https://issues.apache.org/jira/browse/HBASE-14122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640025#comment-14640025 ]
Hadoop QA commented on HBASE-14122: ----------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12746938/HBASE-14122-v2.patch against master branch at commit dad4cad30e5b0c69694ee90908ad8e74c592d821. ATTACHMENT ID: 12746938 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 8 new or modified tests. {color:green}+1 hadoop versions{color}. The patch compiles with all supported hadoop versions (2.4.0 2.4.1 2.5.0 2.5.1 2.5.2 2.6.0 2.7.0) {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 protoc{color}. The applied patch does not increase the total number of protoc compiler warnings. {color:red}-1 javadoc{color}. The javadoc tool appears to have generated 1 warning messages. {color:red}-1 checkstyle{color}. The applied patch generated 1867 checkstyle errors (more than the master's current 1866 errors). {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 2.0.3) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:red}-1 lineLengths{color}. The patch introduces the following lines longer than 100: + * <code>rpc getSecurityCapabilities(.hbase.pb.SecurityCapabilitiesRequest) returns (.hbase.pb.SecurityCapabilitiesResponse);</code> + * <code>rpc getSecurityCapabilities(.hbase.pb.SecurityCapabilitiesRequest) returns (.hbase.pb.SecurityCapabilitiesResponse);</code> {color:green}+1 site{color}. The mvn post-site goal succeeds with this patch. {color:red}-1 core tests{color}. The patch failed these unit tests: org.apache.hadoop.hbase.security.access.TestWithDisabledAuthorization {color:red}-1 core zombie tests{color}. There are 1 zombie test(s): at org.apache.hadoop.hbase.coprocessor.TestOpenTableInCoprocessor.testCoprocessorCanCreateConnectionToRemoteTableWithCustomPool(TestOpenTableInCoprocessor.java:145) Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/14877//testReport/ Release Findbugs (version 2.0.3) warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/14877//artifact/patchprocess/newFindbugsWarnings.html Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/14877//artifact/patchprocess/checkstyle-aggregate.html Javadoc warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/14877//artifact/patchprocess/patchJavadocWarnings.txt Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/14877//console This message is automatically generated. > 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-v2-0.98.patch, > HBASE-14122-v2-branch-1.patch, HBASE-14122-v2.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)