You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "dhruba borthakur (JIRA)" <ji...@apache.org> on 2009/07/15 00:09:14 UTC

[jira] Updated: (HDFS-487) HDFS should expose a fileid to uniquely identify a file

     [ https://issues.apache.org/jira/browse/HDFS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

dhruba borthakur updated HDFS-487:
----------------------------------

    Attachment: fileid1.txt

This patch implements a 64 bit fileid per file. It uses the already existing generation stamp counter to populate this field. 

One major question that is unanswered by this patch: what to do with files that were created by older versions of hadoop. I think a good answer will be assign them unique fileids.

> 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.