[
https://issues.apache.org/jira/browse/HDFS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731670#action_12731670
]
Raghu Angadi commented on HDFS-487:
-----------------------------------
So truncating a file would change the fileid?
btw, 'distcp -update' is expected guarantee just that 'copy-if-modified' and
nothing else.. just like any rsync or other sync that rely modification files
and file lengths (by default). If user wants to handle other cases, then they
should ask distcp to check file checksums.
I am still not clear about block placement use case.. may be it can use id of
the first block (it comes for free).
Even for hardlinks I don't see how fileids help...
> HDFS should expose a fileid to uniquely identify a file
> -------------------------------------------------------
>
> Key: HDFS-487
> URL: https://issues.apache.org/jira/browse/HDFS-487
> Project: Hadoop HDFS
> Issue Type: New Feature
> Reporter: dhruba borthakur
> Assignee: dhruba borthakur
> Attachments: fileid1.txt
>
>
> HDFS should expose a id that uniquely identifies a file. This helps in
> developing applications that work correctly even when files are moved from
> one directory to another. A typical use-case is to make the Pluggable Block
> Placement Policy (HDFS-385) use fileid instead of filename.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
