[
https://issues.apache.org/jira/browse/HBASE-11158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16236641#comment-16236641
]
Sean Busbey commented on HBASE-11158:
-------------------------------------
It looks like the upgrade command no longer exists.
{code}
Busbey-MBA:hbase-2.0.0-alpha4 busbey$ ./bin/hbase upgrade -h
This command was used to upgrade to HBase 0.96, it was removed in HBase 2.0.0.
Please follow the documentation at http://hbase.apache.org/book.html#upgrading.
{code}
close this out?
> bin/hbase upgrade -check should also check compression codecs
> -------------------------------------------------------------
>
> Key: HBASE-11158
> URL: https://issues.apache.org/jira/browse/HBASE-11158
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.99.0
> Reporter: Jean-Marc Spaggiari
> Priority: Major
>
> When upgrading insitu from 0.94 to 0.96 or 0.98 codecs are usually already
> there in the servers so it's all fine.
> But when doing an upgrade by moving the data from one cluster to a brand new
> one, compression codecs might be missing.
> bin/hbase upgrade -check will not report any missing codec, but HBase will
> not be able to start after the upgrade because the codes are missing.
> I think bin/hbase upgrade -check should check the compression codecs
> configured on the tables and make sure they are available on the new cluster.
> f not, it should be reported.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
