hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4502) WebHdfsFileSystem handling of ifile field breaks compatibility and breaks HttpFS
Date Mon, 18 Feb 2013 23:37:13 GMT

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

Tsz Wo (Nicholas), SZE commented on HDFS-4502:

> ... BTW I don't think the json-schema IEFT draft is relevant as we are not using it for
defining the JSON payloads WebHDFS suppport. 

We indeed use the draft in our WebHDFS REST API.  In [Section JSON Schemas|http://hadoop.apache.org/docs/r1.0.4/webhdfs.html#JSON+Schemas],
we did say, "The JSON schemas are shown below. See draft-zyp-json-schema-03 for the syntax
definitions of the JSON schemas."

> Also, would please answer my last question "Do we need it exposed in WebHDFS REST API?"?

Sorry.  Currently, we may not need to expose fileId in WebHDFS.  Let's keep fileId for internal
use only.
> WebHdfsFileSystem handling of ifile field breaks compatibility and breaks HttpFS
> --------------------------------------------------------------------------------
>                 Key: HDFS-4502
>                 URL: https://issues.apache.org/jira/browse/HDFS-4502
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: webhdfs
>    Affects Versions: 3.0.0
>            Reporter: Alejandro Abdelnur
>            Assignee: Brandon Li
>            Priority: Blocker
>         Attachments: HDFS-4502.patch
> HDFS-4340 introduced a new field {{fileId}} in WebHDFS FileStatus JSON representation.
> There are a two issues with this:
> * This is changing the WebHDFS REST API, this has not been documented
> * WebHdfsFileSystem should not fail when that field is not present (This is the case
when using HttpFS against a FS implementation -other than HDFS- which does not handle fileId)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message