[
https://issues.apache.org/jira/browse/HDFS-7878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353776#comment-14353776
]
Jing Zhao commented on HDFS-7878:
---------------------------------
Thanks for the comments, Colin.
bq. What if the file is deleted and re-created in between calling getFileStatus
and calling getFileId?
Could you please add more details here? Note that the {{getFileId}} API in the
current patch only calls {{getFileStatus}} and returns the inode id field
contained in the HdfsFileStatus. Or you mean the client is making both calls
separately? Then why the subclass approach can solve this?
> API - expose an unique file identifier
> --------------------------------------
>
> Key: HDFS-7878
> URL: https://issues.apache.org/jira/browse/HDFS-7878
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Attachments: HDFS-7878.01.patch, HDFS-7878.02.patch, HDFS-7878.patch
>
>
> See HDFS-487.
> Even though that is resolved as duplicate, the ID is actually not exposed by
> the JIRA it supposedly duplicates.
> INode ID for the file should be easy to expose; alternatively ID could be
> derived from block IDs, to account for appends...
> This is useful e.g. for cache key by file, to make sure cache stays correct
> when file is overwritten.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
