hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-1867) Tool to regenerate an hbase table from the data files
Date Fri, 25 Sep 2009 05:06:15 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12759376#action_12759376
] 

stack commented on HBASE-1867:
------------------------------

Above is fine except the bit about users being prompted for instructions to move the table
aside.. .how about we just move it aside and tell user we did it rather than do user interaction
messing in script

> 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 
>            Priority: Minor
>
> 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.


Mime
View raw message