[
https://issues.apache.org/jira/browse/HDFS-7997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14383666#comment-14383666
]
Hadoop QA commented on HDFS-7997:
---------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12707713/HDFS-7997-001.patch
against trunk revision af618f2.
{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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. There were no new javadoc 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 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 core tests{color}. The patch failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.server.namenode.snapshot.TestOpenFilesWithSnapshot
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/10085//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HDFS-Build/10085//console
This message is automatically generated.
> The first non-existing xattr should also throw IOException
> ----------------------------------------------------------
>
> Key: HDFS-7997
> URL: https://issues.apache.org/jira/browse/HDFS-7997
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: zhouyingchao
> Assignee: zhouyingchao
> Attachments: HDFS-7997-001.patch
>
>
> We use the following code snippet to get/set xattrs. However, if there are no
> xattrs have ever been set, the first getXAttr returns null and the second one
> just throws exception with message like "At least one of the attributes
> provided was not found.". This is not expected, we believe they should
> behave in the same way - i.e either both getXAttr returns null or both
> getXAttr throw exception with the message "... not found". We will provide a
> patch to make them both throw exception.
> ....
> attrValueNM = fs.getXAttr(path, "nm");
> if (attrValueNM == null) {
> fs.setXAttr("nm", DEFAULT_VALUE);
> }
> attrValueNN = fs.getXAttr(path, "nn");
> if (attrValueNN == null) {
> fs.setXAttr("nn", DEFAULT_VALUE);
> }
> ....
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
