[HDFS-6464] Support multiple xattr.name parameters for WebHDFS getXAttrs.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0.0-alpha1
• Fix Version/s: 2.5.0
• Component/s: webhdfs
• Hadoop Flags: Reviewed
• Assignee: Yi Liu
• Reporter: Yi Liu
• Created: 29/May/14 01:38
• Updated: 12/May/16 18:15
• Resolved: 06/Jun/14 03:53

Description

For WebHDFS getXAttrs through names, right now the entire list is passed to the client side and then filtered, which is not the best choice since it's inefficient and precludes us from doing server-side smarts on par with the Java APIs.
Furthermore, if some xattrs doesn't exist, server side should return error.

Issue Links

• blocks: HDFS-6422 getfattr in CLI doesn't throw exception or return non-0 return code when xattr doesn't exist
• is related to: HDFS-2006 ability to support storing extended attributes per file
• is required by: HDFS-6430 HTTPFS - Implement XAttr support