Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BCCF9C10B for ; Wed, 16 May 2012 03:30:50 +0000 (UTC) Received: (qmail 16566 invoked by uid 500); 16 May 2012 03:30:50 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 15939 invoked by uid 500); 16 May 2012 03:30:47 -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 15633 invoked by uid 99); 16 May 2012 03:30:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 03:30:46 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 May 2012 03:30:44 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 7D4FF67D2 for ; Wed, 16 May 2012 03:30:23 +0000 (UTC) Date: Wed, 16 May 2012 03:30:23 +0000 (UTC) From: "Sanjay Radia (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: <912531708.2396.1337139023514.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <2068361121.27846.1336151688971.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (HDFS-3370) HDFS hardlink MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13276415#comment-13276415 ] Sanjay Radia commented on HDFS-3370: ------------------------------------ * I see the additional complexity in quotas because HDFS quotas are directory based (like several file systems). I think this is addressable if we double count the quotas along both path. * Permissions are not a problem since the file retains the file permissions and both paths to the file offer their own permissions. * I don't understand Srivas's rename example. Srivas, in MapR I suspect that renames are only allowed within a volume and such hard links would be supported only within a volume. Can you explain the problem with some more details. > HDFS hardlink > ------------- > > Key: HDFS-3370 > URL: https://issues.apache.org/jira/browse/HDFS-3370 > Project: Hadoop HDFS > Issue Type: New Feature > Reporter: Hairong Kuang > Assignee: Liyin Tang > Attachments: HDFS-HardLink.pdf > > > We'd like to add a new feature hardlink to HDFS that allows harlinked files to share data without copying. Currently we will support hardlinking only closed files, but it could be extended to unclosed files as well. > Among many potential use cases of the feature, the following two are primarily used in facebook: > 1. This provides a lightweight way for applications like hbase to create a snapshot; > 2. This also allows an application like Hive to move a table to a different directory without breaking current running hive queries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira