You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2014/06/07 17:54:01 UTC
[jira] [Updated] (HDFS-6500) Snapshot shouldn't be removed silently
after renaming to an existing snapshot
[ https://issues.apache.org/jira/browse/HDFS-6500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tsz Wo Nicholas Sze updated HDFS-6500:
--------------------------------------
Attachment: h6500_20140607.patch
h6500_20140607.patch: changes the > to >= and adds new tests.
> Snapshot shouldn't be removed silently after renaming to an existing snapshot
> -----------------------------------------------------------------------------
>
> Key: HDFS-6500
> URL: https://issues.apache.org/jira/browse/HDFS-6500
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: snapshots
> Affects Versions: 2.4.0
> Reporter: Junping Du
> Assignee: Tsz Wo Nicholas Sze
> Priority: Blocker
> Attachments: h6500_20140607.patch
>
>
> Assume you have two snapshots for /dir: s1, s2, when you do "hdfs dfs
> -renameSnapshot /dir s2 s1" which means you want to rename s2 to s1. It will cause s2 been dropped silently and s1 still keep the previous one. This is very confusing and easily cause wrong operation.
> The right behavior should be providing a warning to remind user that the target name is already existed and do nothing. If user do want to overlap s1, he should add some option (i.e. "-f") or delete s1 first.
--
This message was sent by Atlassian JIRA
(v6.2#6252)