Norbert Burger 2012-10-15, 15:25
Stack 2012-10-15, 18:57
Tianying Chang 2013-02-21, 18:06
Harsh J 2013-02-21, 18:12
I already fixed this script to make it working mid last year, we used it in our production since. Also we don't need to run hbck -fix afterwards. The script works for both 92 and 94. I will publish my patch.
From: Harsh J [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 21, 2013 10:13 AM
To: [EMAIL PROTECTED]
Subject: Re: status of bin/rename_table.rb
If the need is urgent, try out the solution from Shrijeet at
https://issues.apache.org/jira/browse/HBASE-643 (see my comment there at around end). We tried it out earlier today for another purpose, and it had a few hitches but nothing unfixable by "hbck -fix".
On Thu, Feb 21, 2013 at 11:36 PM, Tianying Chang <[EMAIL PROTECTED]> wrote:
> Our customers need to use rename_table to solve an issue in our production cluster. Since 92 does not have it, we copied it from CDH3. However it does not work. I then found several issues with it, and fixed them. We used it in our production cluster to rename some very big tables. Even when the cluster was shutdown during the rename_table (test purpose), the script will continue the rename and succeed if invoking the same rename command again after cluster is back.
> I think it is helpful to have rename_table script handy. I can open a jira and attach my patch.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of
> Sent: Monday, October 15, 2012 11:57 AM
> To: [EMAIL PROTECTED]
> Subject: Re: status of bin/rename_table.rb
> On Mon, Oct 15, 2012 at 8:25 AM, Norbert Burger <[EMAIL PROTECTED]> wrote:
>> Hi folks,
>> Does anyone have a good working process for renaming tables? From
>> the links below, I gather that the bin/rename_table.rb (last included
>> 0.90.x) had a few issues.
>> http://search-hadoop.com/m/uAfm51RZCl42/Hbase%253A+Table+rename&subj>> H
>> I tried rename_table.rb a few times with some of our larger tables
>> and did have some issues with .META., but it's not clear to me if
>> these issues were caused by rename_table or not.
> The script has gone stale. It is removed in trunk and should have probably been removed earlier.
> That said, its pretty basic what it does. What sort of issues are you seeing? Does running disable/enable help?