Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Message-ID: <1822762692.1247609354845.JavaMail.jira@brutus>
Date: Tue, 14 Jul 2009 15:09:14 -0700 (PDT)
From: "dhruba borthakur (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Subject: [jira] Updated: (HDFS-487) HDFS should expose a fileid to uniquely
 identify a file
In-Reply-To: <1224413592.1247271675279.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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