hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (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:01:13 GMT

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

Alejandro Abdelnur commented on HDFS-4502:
------------------------------------------

Thanks Nicholas, thanks for filing the JIRA to clarify. 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.


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



                
> 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

Mime
View raw message