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

Hudson commented on HDFS-4502:
------------------------------

Integrated in Hadoop-trunk-Commit #3369 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/3369/])
    HDFS-4502. JsonUtil.toFileStatus(..) should check if the fileId property 
exists.  Contributed by Brandon Li (Revision 1448502)

     Result = SUCCESS
szetszwo : 
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1448502
Files : 
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* 
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/web/JsonUtil.java

                
> 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
>             Fix For: 3.0.0
>
>         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

Reply via email to