[
https://issues.apache.org/jira/browse/HBASE-7896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13584558#comment-13584558
]
Tianying Chang commented on HBASE-7896:
---------------------------------------
The high level summary of renaming a table is like this: create hdfs dir for
the new table; rename the Hfile from old table dir into new table dir; delete
the entry for old table from META; insert the entry for the new table into
META; manipulate zookeeper to create a znode for the new table. Because this is
an un-conventional way of "creating" a new table, the master is not aware of
the new table. That is why I manipulate the zookeeper by explicitly inserting a
znode for the new table. But master still does not read in the full information
of the new table, so it is not REALLY enabled. By inserting the znode with
enable state, we can make it officially enabled by calling disable/enable
sequence on this new table without needing to restart master, because it
invoked the master to learn of the new table.
This is just my quick way to make rename_table.rb work for our production
cluster. My next step plan is 1. make master aware of the newly renamed table
immediately without explicit znode manipulation and table disable/enable. This
will probably need to expose some API from Master 2. make rename_table as 2pc
with roll back capability.
> make rename_table working in 92/94
> ----------------------------------
>
> Key: HBASE-7896
> URL: https://issues.apache.org/jira/browse/HBASE-7896
> Project: HBase
> Issue Type: Bug
> Components: scripts
> Affects Versions: 0.92.2, 0.94.5
> Reporter: Tianying Chang
> Assignee: Tianying Chang
> Fix For: 0.92.2, 0.94.6
>
> Attachments: rename_table.rb
>
>
> The rename_table function is very useful for our customers. However,
> rename_table.rb does not work for 92/94. It has several bugs. It will be
> useful to fix them so that users can solve their problems.
--
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
