[ 
https://issues.apache.org/jira/browse/HDFS-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871450#action_12871450
 ] 

Hadoop QA commented on HDFS-992:
--------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12445203/h992-28.patch
  against trunk revision 948260.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 36 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    -1 javac.  The patch appears to cause tar ant target to fail.

    -1 findbugs.  The patch appears to cause Findbugs to fail.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    -1 core tests.  The patch failed core unit tests.

    -1 contrib tests.  The patch failed contrib unit tests.

Test results: 
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/377/testReport/
Checkstyle results: 
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/377/artifact/trunk/build/test/checkstyle-errors.html
Console output: 
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/377/console

This message is automatically generated.

> Re-factor block access token implementation to conform to the generic Token 
> interface in Common
> -----------------------------------------------------------------------------------------------
>
>                 Key: HDFS-992
>                 URL: https://issues.apache.org/jira/browse/HDFS-992
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>          Components: security
>            Reporter: Kan Zhang
>            Assignee: Kan Zhang
>         Attachments: h992-12.patch, h992-18.patch, h992-20.patch, 
> h992-21.patch, h992-23.patch, h992-26.patch, h992-27.patch, h992-28.patch, 
> h992-BK-0.20-07.1.patch, h992-BK-0.20-07.patch
>
>
> This makes it possible to use block access token as shared key for 
> client-to-datanode authentication over RPC. However, access authorization is 
> still based on block access token semantics.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to