[
https://issues.apache.org/jira/browse/HBASE-7218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537317#comment-13537317
]
Jesse Yates commented on HBASE-7218:
------------------------------------
Since we are just doing copies for the rename, this should be fine except in
cases of cloning/export, which should recieve some thorough commenting to avoid
contention. However, I don't think we need to have server-side exclusion of the
actions - your a bad admin if you try to export a snapshot and rename it at the
the same time.
To the end of helping admins, maybe a follow-on jira to surface ALL running
snapshot operations to the UI?
> Rename Snapshot
> ---------------
>
> Key: HBASE-7218
> URL: https://issues.apache.org/jira/browse/HBASE-7218
> Project: HBase
> Issue Type: Sub-task
> Components: snapshots
> Affects Versions: hbase-6055
> Reporter: Matteo Bertozzi
> Assignee: Matteo Bertozzi
> Priority: Minor
> Fix For: hbase-6055
>
> Attachments: HBASE-7218-v0.patch, HBASE-7218-v1.patch
>
>
> Add the ability to rename a snapshot.
> HBaseAdmin.renameSnapshot(oldName, newName)
> shell: snapshot_rename 'oldName', 'newName'
--
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
