[
https://issues.apache.org/jira/browse/HDFS-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031904#comment-14031904
]
Hudson commented on HDFS-6464:
------------------------------
FAILURE: Integrated in Hadoop-trunk-Commit #5707 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/5707/])
Moved CHANGES.txt entries of MAPREDUCE-5898, MAPREDUCE-5920, HDFS-6464,
HDFS-6375 from trunk to 2.5 section on merging HDFS-2006 to branch-2
(umamahesh:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1602699)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
> Support multiple xattr.name parameters for WebHDFS getXAttrs.
> -------------------------------------------------------------
>
> Key: HDFS-6464
> URL: https://issues.apache.org/jira/browse/HDFS-6464
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: webhdfs
> Affects Versions: 3.0.0
> Reporter: Yi Liu
> Assignee: Yi Liu
> Fix For: 3.0.0, 2.5.0
>
> Attachments: HDFS-6464.1.patch, HDFS-6464.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
