hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "dhruba borthakur (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-487) HDFS should expose a fileid to uniquely identify a file
Date Sun, 20 Sep 2009 06:24:16 GMT

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

dhruba borthakur commented on HDFS-487:

Hi folks, now that HDFS-385 has been committed I would like to resurrect the discussion about
fileids for HDFS files. 

The negative feedback earlier was from Raghu who mentioned that it may be premature to introduce
the concept of a fileid. In some sense, this is true but is more of a chicken-and-egg problem.
The existence of a fileid simplifies many-a-applications. Can we have some discussion on what
the possible dis-advantages of introducing a fileid might be?


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

View raw message