[
https://issues.apache.org/jira/browse/HBASE-8015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654601#comment-13654601
]
stack commented on HBASE-8015:
------------------------------
bq. It should be noted that the rename is done by first taking snapshot of the
table and cloning to the new table name.
No it shouldn't. There was no consensus on the list and this is an exploratory
effort so no need of constraint.
One thought I had was that if all tables need to be moved, mayhaps we just say
snapshots are broke on upgrade or rather than a tool for table rename, instead,
we'd have a tool that did surgery on snapshots to adjust them to match the new
layout (advantage of this latter is that it can be done offline, not inline
with migration -- though, I have no idea this would work... ask the
snapshotters Jon, Matteo and Jesse).
> Support for Namespaces
> ----------------------
>
> Key: HBASE-8015
> URL: https://issues.apache.org/jira/browse/HBASE-8015
> Project: HBase
> Issue Type: New Feature
> Reporter: Francis Liu
> Assignee: Francis Liu
> Attachments: HBASE-8015_draft_94.patch, Namespace Design.pdf
>
>
--
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
