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-62) [hbase] Allow user add arbitrary key/value pairs to table and column descriptors
Date Thu, 03 Jul 2008 23:49:45 GMT

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

stack commented on HBASE-62:

Thanks for new patch Andrew.

I've been playing around with the migration.  Its that old story where you need the old class
around to deserialize but the new class is in the way.  I've started up a little package under
o.a.h.h.util named migration.v4.   In it, I'll add classes need to do the v3 to v4 migration.
 WIll need to iterate over all .META. regions using new tools I need to add to MetaUtils.
 Will get the info:regioninfo column bytes and feed them to a subclass of HRI, one that has
a diffferent deserializer.  This new deserializer inserts a subclass of HTD that also has
a different deserializer, one that can read v3 HTDs.  It copies the v3 to a v4 HTD.  Then
we call the default HRI serializer -- which will invoke the v4 HTD serializer -- and insert
back into .META.

One hiccup is that we might have to do the v4 migration ahead of the v3 migration in tests.

I'm a little worried that subclassing HRI and HTD in migration is too brittle.  Will think
on it over the w/e.

> [hbase] Allow user add arbitrary key/value pairs to table and column descriptors
> --------------------------------------------------------------------------------
>                 Key: HBASE-62
>                 URL: https://issues.apache.org/jira/browse/HBASE-62
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>            Assignee: Andrew Purtell
>            Priority: Trivial
>         Attachments: hbase-62-r673137.patch, hbase-62-r673264.patch, hbase-62-r673356.patch
> Folks have asked if they can tag columns and tables with markings of their own designation.
 Examples include 'type' and 'descriptiion'. 

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

View raw message