You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2009/11/09 16:47:32 UTC
[jira] Updated: (HBASE-1867) Tool to regenerate an hbase table from
the data files
[ https://issues.apache.org/jira/browse/HBASE-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-1867:
-------------------------
Resolution: Fixed
Fix Version/s: 0.20.2
Status: Resolved (was: Patch Available)
Added this script. Its of general utility.
> Tool to regenerate an hbase table from the data files
> -----------------------------------------------------
>
> Key: HBASE-1867
> URL: https://issues.apache.org/jira/browse/HBASE-1867
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: util
> Affects Versions: 0.20.0
> Reporter: elsif
> Assignee: stack
> Priority: Minor
> Fix For: 0.20.2, 0.21.0
>
> Attachments: add_table.rb
>
>
> The purpose of this JIRA is provide a place to coordinate the development of a utility that will regenerate an hbase table from the data files.
> Here are some comments from stack on this subject from the hbase-user mailing list:
> Well, in the bin directory, there are scripts that do various things with
> the .META. (copy a table, move a table, load a table whose source is hfiles
> written by a mapreduce job; i.e. hbase-48).
> So, to 'regenerate an hbase table from the data files', you'd need to do
> something like the following:
> + delete all exisiting table references from .META.
> + move the backuped up table into position under hbase.rootdir
> + per region under hbase.rootdir, add an entry to .META. Do this by opening
> the .regioninfo file. Its content is needed to generate the rowid for
> .META. and its value becomes the info:regioninfo cell value.
> HBase does not need to be down. On next .META. scan, the newly added
> regions will be noticed. They won't have associated info:server and
> info:startcode entries so master will go ahead and assign them and you
> should be up and running.
> Code-wise, a study of copy_table.rb (this uses old api ... needs updating
> but the concepts are the same) and loadtable.rb would probably be fruitful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.