[
https://issues.apache.org/jira/browse/HDFS-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016140#comment-14016140
]
Yi Liu commented on HDFS-6464:
------------------------------
Thanks [~clamb] for your comments. BTW, the 2 tests failure are not related to
the patch.
{quote}
The change to XAttrHelper.java is just white space so you can leave it out.
{quote}
It's tabs, so I modify it.
{quote}
In NameNodeWebHdfsMethods, when would xattrName.getXAttrName be null in:
if (xattrName.getXAttrName() != null) {
names.add(xattrName.getXAttrName());
{quote}
It happens when there is no value for some xattr.name parameter in HTTP
request. For example
{code}xattr.name=<XATTRNAME1>&xattr.name=&xattr.name=<XATTRNAME3>{code}
> 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.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)
