[
https://issues.apache.org/jira/browse/HDFS-6422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Charles Lamb updated HDFS-6422:
-------------------------------
Attachment: HDFS-6422.010.patch
[~umamaheswararao],
Thanks for the review. I agree with your suggestion to add a test for remove
xattr in TestRetryCacheWIthHA and the latest patch does that. Jenkins passed
everything except that test because there is no way to have it apply the binary
file so once that's checked in it should all pass.
> getfattr in CLI doesn't throw exception or return non-0 return code when
> xattr doesn't exist
> --------------------------------------------------------------------------------------------
>
> Key: HDFS-6422
> URL: https://issues.apache.org/jira/browse/HDFS-6422
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.5.0
> Reporter: Charles Lamb
> Assignee: Charles Lamb
> Priority: Blocker
> Attachments: HDFS-6422.005.patch, HDFS-6422.006.patch,
> HDFS-6422.007.patch, HDFS-6422.008.patch, HDFS-6422.009.patch,
> HDFS-6422.010.patch, HDFS-6422.1.patch, HDFS-6422.2.patch, HDFS-6422.3.patch,
> HDFS-6474.4.patch, editsStored
>
>
> If you do
> hdfs dfs -getfattr -n user.blah /foo
> and user.blah doesn't exist, the command prints
> # file: /foo
> and a 0 return code.
> It should print an exception and return a non-0 return code instead.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
