[ https://issues.apache.org/jira/browse/HDFS-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017727#comment-14017727 ]
Hadoop QA commented on HDFS-6464: --------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12648313/HDFS-6464.1.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. There were no new javadoc warning messages. {color:green}+1 eclipse:eclipse{color}. The patch built with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-hdfs-project/hadoop-hdfs. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-HDFS-Build/7036//testReport/ Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/7036//console This message is automatically generated. > 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 > > 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)