[
https://issues.apache.org/jira/browse/HADOOP-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551198
]
Bryan Duxbury commented on HADOOP-2394:
---------------------------------------
What do we think of creating Rails-esque migration scripts for each version
change? Each migration script would have to know how to read the previous
version's data and write the current version. Then we can add a version number
to any files we store in HDFS to indicate what version it was created at.
When you deploy a new version of HBase, you first need to run the migration
script. Once the migration is completed successfully, you should be able to
start the new version of HBase. Also, the migration script should prefer not
overwriting the existing files, instead creating new ones. That way, we're less
likely to make some mistake that causes the old data to get lost while the new
data is being re-written.
> Add supprt for migrating between hbase versions
> -----------------------------------------------
>
> Key: HADOOP-2394
> URL: https://issues.apache.org/jira/browse/HADOOP-2394
> Project: Hadoop
> Issue Type: Improvement
> Components: contrib/hbase
> Reporter: Johan Oskarsson
>
> If Hbase is to be used to serve data to live systems we would need a way to
> upgrade both the underlying hadoop installation and hbase to newer versions
> with minimal downtime.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
