zhouyingchao created HDFS-7997:
----------------------------------
Summary: 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
Reporter: zhouyingchao
Assignee: zhouyingchao
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)
