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 Fri, 31 Jul 2009 21:42:14 GMT

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

stack commented on HBASE-1726:

Yeah, usually we'd add the old HTD class under migration.nineteen and then use it in deserializing
the bytes we got scanning.

We're not doing that in this migration because since HTD and HCD were moved to be backed my
a Map, then rare is need to read the old data with the old class (Does that make sense?  Most
Key/Values are in the map now).  Unfortunately not all are in the Map.  That seems to be the
case here?

Its a pain having to put in place the old classes.  Can you not do something simple like set
a flag on migration that says "I'm migrating a ITHBase".  Then down in the scan of catalog
regions, add in the missing 'indexed' flag.

Or, sounds like you figured a trick already to move forward ITHBase.  Mind adding documentation
to the wiki on how you did it?  Then we can close this issue?

THanks Clint.

> 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