[
https://issues.apache.org/jira/browse/HDFS-4502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581872#comment-13581872
]
Alejandro Abdelnur commented on HDFS-4502:
------------------------------------------
Trying to be a bit more clear, I understand fileId is not part of the Web HDFS
REST API spec. I'm trying to understand why is useful to have it as an
undocumented 'additional field'. And why WebHdfsFileSystem uses a class that is
private to DistributedFileSystem.
> 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
