[
https://issues.apache.org/jira/browse/HBASE-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613805#action_12613805
]
stack commented on HBASE-62:
----------------------------
I've been working on the necessary migration. Its ugly mixing old and new
versions of about ten classes. Almost done though.
We could punt bringing in this patch but the migration would still be ugly,
just postponed. Might be uglier even if lots of on-filesystems in 0.3 hbase.
This (painful) patch opens our easily doing other HTD extensions because it
introduces HTD versioning (e.g. moving table schema out of HTD). Also adds
read-only hbase table. Its kinda sweet.
Regards migrations, after bringing in this patch, I think we should start over
with migrations; they're complicated enough now involving 5 distinct steps. It
would mean that you could not go from old hbase 0.16.x through to 0.3. You'd
have to install 0.2 to bring you up to 0.2 hbase; then install 0.3 hbase to
migrate from 0.2 to 0.3.
> [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
> Fix For: 0.2.0
>
> Attachments: hbase-62-676775.patch, hbase-62-r673356.patch,
> hbase-62-r673635.patch, hbase-62-r676786.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.
