[
https://issues.apache.org/jira/browse/HDFS-5212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13767993#comment-13767993
]
Hadoop QA commented on HDFS-5212:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12603263/HDFS-5212.001.patch
against trunk revision .
{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 test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:red}-1 eclipse:eclipse{color}. The patch failed to build with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:red}-1 release audit{color}. The applied patch generated 1
release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-nfs hadoop-hdfs-project/hadoop-hdfs-nfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/4977//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/4977//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4977//console
This message is automatically generated.
> Refactor RpcMessage and NFS3Response to support different types of
> authentication information
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-5212
> URL: https://issues.apache.org/jira/browse/HDFS-5212
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: nfs
> Reporter: Jing Zhao
> Assignee: Jing Zhao
> Attachments: HDFS-5212.001.patch
>
>
> Currently the authentication information is hard coded in RpcMessage (and its
> subclasses) and NFS3Response (and its subclasses) as AuthFlavor value and
> empty byte array. We need to refactor this part of code to support different
> types of authentication information.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
