Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Thu, 5 Jun 2014 11:53:02 +0000 (UTC)
From: "Uma Maheswara Rao G (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12717192.1401327495549.75578.1401969182341@arcas>
In-Reply-To: <JIRA.12717192.1401327495549@arcas>
References: <JIRA.12717192.1401327495549@arcas>
Subject: [jira] [Commented] (HDFS-6464) Support multiple xattr.name
 parameters for WebHDFS getXAttrs.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HDFS-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018710#comment-14018710 ] 

Uma Maheswara Rao G commented on HDFS-6464:
-------------------------------------------

+1 patch looks good to me. I will commit the patch shortly.

> 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)