Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 1 Nov 2011 05:38:34 +0000 (UTC)
From: "Alejandro Abdelnur (Commented) (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: 
 <1463844511.44689.1320125914322.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <209743167.24833.1315389790560.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HDFS-2316) webhdfs: a complete FileSystem
 implementation for accessing HDFS over HTTP
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Alejandro Abdelnur commented on HDFS-2316:
------------------------------------------

I've been running tests to validate HTTP REST API compatibility between webhdfs and hoop. Following the issues I've found.


* FileStatus JSON payload has elements that are not part of the FileStatus interface. The WebhdfsFileSystem client expects those elements and fails if they are not present. These elements are: localName, isSymlink, symlink. These elements are not later used and they are lost when creating a FileStatus in WebhdfsFileSystem. Either those elements should not be in JSON payload (my preference) or they should not be required by the WebhdfsFileSystem.

* delete, rename, mkdirs, setReplication JSON responses use 'boolean' as element name, they should use the operation name as it is more descriptive.

* FileChecksum JSON serialization is using the classname in the JSON payload, it should not, it should be something like:

{code}
{
  "algorithm" : "foo",
  "bytes" : "hexabytes",
  "length" : 1000
}
{code}

* Same as FileChecksum JSON for ContentSummary JSON.

                
> webhdfs: a complete FileSystem implementation for accessing HDFS over HTTP
> --------------------------------------------------------------------------
>
>                 Key: HDFS-2316
>                 URL: https://issues.apache.org/jira/browse/HDFS-2316
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>         Attachments: WebHdfsAPI20111020.pdf
>
>
> We current have hftp for accessing HDFS over HTTP.  However, hftp is a read-only FileSystem and does not provide "write" accesses.
> In HDFS-2284, we propose to have webhdfs for providing a complete FileSystem implementation for accessing HDFS over HTTP.  The is the umbrella JIRA for the tasks.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira