hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-14400) Fix HBase RPC protection documentation
Date Thu, 10 Sep 2015 22:31:46 GMT

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

Hadoop QA commented on HBASE-14400:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  against master branch at commit 4418f3e02528d6b734b31d225adb45dfb29431fe.
  ATTACHMENT ID: 12755207

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {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 2.7.1)

    {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:green}+1 javadoc{color}.  The javadoc tool did not generate any warning messages.

                {color:red}-1 checkstyle{color}.  The applied patch generated 1835 checkstyle
errors (more than the master's current 1834 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:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

  {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:

     {color:red}-1 core zombie tests{color}.  There are 3 zombie test(s): 	at org.apache.hadoop.hbase.client.TestCloneSnapshotFromClient.testCloneLinksAfterDelete(TestCloneSnapshotFromClient.java:209)
	at org.apache.hadoop.hbase.client.TestMobCloneSnapshotFromClient.testCloneSnapshot(TestMobCloneSnapshotFromClient.java:175)
	at org.apache.hadoop.hbase.client.TestMobCloneSnapshotFromClient.testCloneSnapshotCrossNamespace(TestMobCloneSnapshotFromClient.java:190)
	at org.apache.hadoop.hbase.client.TestReplicasClient.testScanWithReplicas(TestReplicasClient.java:600)

Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/15534//testReport/
Release Findbugs (version 2.0.3) 	warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/15534//artifact/patchprocess/newFindbugsWarnings.html
Checkstyle Errors: https://builds.apache.org/job/PreCommit-HBASE-Build/15534//artifact/patchprocess/checkstyle-aggregate.html

                Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/15534//console

This message is automatically generated.

> Fix HBase RPC protection documentation
> --------------------------------------
>                 Key: HBASE-14400
>                 URL: https://issues.apache.org/jira/browse/HBASE-14400
>             Project: HBase
>          Issue Type: Bug
>          Components: encryption, rpc, security
>            Reporter: Apekshit Sharma
>            Assignee: Apekshit Sharma
>            Priority: Critical
>             Fix For: 2.0.0, 1.3.0, 1.2.1
>         Attachments: HBASE-14400-master.patch
> HBase configuration 'hbase.rpc.protection' can be set to 'authentication', 'integrity'
or 'privacy'.
> "authentication means authentication only and no integrity or privacy; integrity implies
> authentication and integrity are enabled; and privacy implies all of
> authentication, integrity and privacy are enabled."
> However hbase ref guide incorrectly suggests in some places to set the value to 'auth-conf'
instead of 'privacy'. Setting value to 'auth-conf' doesn't provide rpc encryption which is
what user wants.
> This jira will fix:
> - documentation: change 'auth-conf' references to 'privacy'
> - SaslUtil to support both set of values (privacy/integrity/authentication and auth-conf/auth-int/auth)
to be backward compatible with what was being suggested till now.
> - change 'hbase.thrift.security.qop' to be consistent with other similar configurations
by using same set of values (privacy/integrity/authentication).

This message was sent by Atlassian JIRA

View raw message