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

Chris Douglas commented on HDFS-10262:
--------------------------------------

For compatibility with existing 2.x clients, the signature for {{getFileId}} 
should not change, and the "fileId" field should still be populated as a long 
in WebHDFS.

> Change HdfsFileStatus::fileId to an opaque identifier
> -----------------------------------------------------
>
>                 Key: HDFS-10262
>                 URL: https://issues.apache.org/jira/browse/HDFS-10262
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs-client, webhdfs
>            Reporter: Chris Douglas
>
> HDFS exposes the INode ID as a long via HdfsFileStatus::getFileId. Since 
> equality is the only valid client operation (sequential/monotonically 
> increasing ids are not guaranteed in any spec; leases do not rely on any 
> other property), this identifier can be opaque instead of assigning it a 
> primitive type in HdfsFileStatus.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to