[
https://issues.apache.org/jira/browse/HDFS-3370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13454170#comment-13454170
]
Jesse Yates commented on HDFS-3370:
-----------------------------------
@Jagane - in short, yes. With the PIT split, any writes up to that point will
go into the snapshot. Obviously, we can't ensure that future writes beyond the
taking of the snapshot end up in the snapshot. Some writes can get dropped
between snapshots though if you don't have your TTLs set correctly, since a
compaction can age-off the writes before the snapshot can be taken. This is
part of an overall backup solution, and not really the concern of the mechanism
for taking snapshots - that's up to you :) Feel free to DM me if you want to
chat more.
> 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
