[
https://issues.apache.org/jira/browse/HDFS-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581843#comment-13581843
]
Tsz Wo (Nicholas), SZE commented on HDFS-4502:
----------------------------------------------
> ... I'm just trying to understand what is the use case for having the fileId
> avail in the FileStatus returned by the WebHDFS REST API.
First of all, I like to emphasize fileId is not in WebHDFS REST API. It is
just that the Namenode implementation of WebHDFS REST API returns fileId as an
additional property.
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.
> 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
