Return-Path: Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: (qmail 35179 invoked from network); 20 Sep 2009 06:24:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 20 Sep 2009 06:24:40 -0000 Received: (qmail 28381 invoked by uid 500); 20 Sep 2009 06:24:40 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 28323 invoked by uid 500); 20 Sep 2009 06:24:40 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 28302 invoked by uid 99); 20 Sep 2009 06:24:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Sep 2009 06:24:40 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 20 Sep 2009 06:24:37 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 11C1A234C044 for ; Sat, 19 Sep 2009 23:24:16 -0700 (PDT) Message-ID: <452570207.1253427856058.JavaMail.jira@brutus> Date: Sat, 19 Sep 2009 23:24:16 -0700 (PDT) From: "dhruba borthakur (JIRA)" To: hdfs-issues@hadoop.apache.org Subject: [jira] Commented: (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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ 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.