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 Tue, 19 Feb 2013 00:07:12 GMT

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

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

Nicholas, thanks for the clarification on the schemas, somehow I've missed/forgot them. Regarding
your comment 'we may not need to expose fileId in WebHDFS', then you mean we should repurpose
this JIRA to undo the 'fileId' field both on the server and client side of WebHDFS?
                
> 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