[HDFS-6422] getfattr in CLI doesn't throw exception or return non-0 return code when xattr doesn't exist

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.5.0, 3.0.0-alpha1
• Fix Version/s: 2.5.0
• Target Version/s: 2.5.0
• Hadoop Flags: Reviewed
• Assignee: Charles Lamb
• Reporter: Charles Lamb
• Created: 16/May/14 22:22
• Updated: 12/May/16 18:14
• Resolved: 23/Jul/14 19:09

Description

If you do

hdfs dfs -getfattr -n user.blah /foo

and user.blah doesn't exist, the command prints

1. file: /foo

and a 0 return code.

It should print an exception and return a non-0 return code instead.

Issue Links

• is blocked by: HDFS-6464 Support multiple xattr.name parameters for WebHDFS getXAttrs.