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-1726) Migration to 0.20 looses index information from HTableDescriptor
Date Thu, 30 Jul 2009 23:13:15 GMT

    [ https://issues.apache.org/jira/browse/HBASE-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737350#action_12737350

stack commented on HBASE-1726:

Good idea Andrew.  Would call each contrib in turn at various stages: before, during, after.
 Lets make an issue but not bother with dev. till needed (smile).

In this case, change should be part of the core migration since transaction was core in 0.19.

So, Clint, with this fix, you were able to migrate a 0.19 THBase to 0.20?  If so, update the
wiki where it says we don't migrate THBase nor ITHBase.

You'd patch http://svn.apache.org/viewvc/hadoop/hbase/trunk/src/java/org/apache/hadoop/hbase/util/Migrate.java?revision=797273.
 See migrate6to7.  You'd probably want to patch the rewriteHRegionInfo method.

> Migration to 0.20 looses index information from HTableDescriptor
> ----------------------------------------------------------------
>                 Key: HBASE-1726
>                 URL: https://issues.apache.org/jira/browse/HBASE-1726
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: contrib
>            Reporter: Clint Morgan
>             Fix For: 0.20.0
> In 0.19 index info was stored as a private field, and written specially in the Writable
impl of HTD. In 0.20 it is stored in the general values map under the key "INDEXES". So migration
needs to read in the old HTD format, and store the indexes in the values map. I wrote a quick
standalone thing to do this. Can someone point me where to plug this into general migration

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message