[
https://issues.apache.org/jira/browse/HDFS-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13595396#comment-13595396
]
Hadoop QA commented on HDFS-4560:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12572428/HDFS-4560.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 1 new
or modified test files.
{color:green}+1 tests included appear to have a timeout.{color}
{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:green}+1 eclipse:eclipse{color}. The patch built 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-hdfs-project/hadoop-hdfs.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/4046//testReport/
Release audit warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/4046//artifact/trunk/patchprocess/patchReleaseAuditProblems.txt
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/4046//console
This message is automatically generated.
> Webhdfs cannot use tokens obtained by another user
> --------------------------------------------------
>
> Key: HDFS-4560
> URL: https://issues.apache.org/jira/browse/HDFS-4560
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 3.0.0, 0.23.7, 2.0.4-beta
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Attachments: HDFS-4560.patch, HDFS-4560.patch
>
>
> Webhdfs passes {{UserParam}} even when a token is being used. The NN will
> construct the UGI from the token and error if the {{UserParam}} does not
> match the token's. This causes problems when a token for user A is used with
> user B's context. This is in contrast to hdfs which will honor the token's
> ugi no matter the client's current context. The passing of a token or user
> params should be mutually exclusive.
--
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
