[
https://issues.apache.org/jira/browse/HDFS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454144#comment-13454144
]
Jagane Sundar commented on HDFS-3370:
-------------------------------------
Thanks for the pointer to HBASE-6055, Jesse. I just skimmed it, but it is an
excellent write-up you have there. Your rationalization for the use of HBASE
Timestamps versus actual Point in Time is well taken. My own experience is with
writing software to backup a single running VM, so my previous comment did talk
about an actual PIT.
I did not catch this in my skimming of HBASE-6055, so maybe you can clarify -
when using HBASE Timestamps to create backups, can we guarantee that the next
backup will include all PUTs that were made after the previous snapshot? No
PUTs will fall through the cracks, right?
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira
