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 Wed, 20 Feb 2013 03:17:15 GMT

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

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

bq. I think your question is: why returning fileId as an additional property in Namenode?
The reason is that HdfsFileStatus requires fileId. If WebHdfsFileSystem does not set it, then
some internal use of HdfsFileStatus may not work.

Nicholas, this is a bit troublesome statement, are you saying that there is code that consumes
a random FileSystem client implementation other than DistributedFileSystem (WebHdfsFileSystem
in this case) and casts the FileStatus to HdfsFileStatus? 

What is the specific use case you have in mind to justify fileId showing up in Web HDFS REST
API response and in a WebHdfsFileSystem instance?

                
> 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: Sub-task
>          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