[
https://issues.apache.org/jira/browse/HBASE-1726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737353#action_12737353
]
Andrew Purtell commented on HBASE-1726:
---------------------------------------
Could do it with annotations and classpath scanning. Then add to wiki and
javadoc instructions to the effect that any user with some contrib should make
sure to put the new contrib version on the classpath along with the new core
jar version before running migration. Migration utility can scan the classpath
for annotated classes which implement a migration interface with methods
preMigration(), migrate(), and postMigration() or similar.
> 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
> process?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
