You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2018/03/02 03:24:00 UTC

[jira] [Resolved] (HBASE-11860) Restore UpgradeTo in order to upgrade a HBase cluster to the latest release

     [ https://issues.apache.org/jira/browse/HBASE-11860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-11860.
---------------------------
    Resolution: REMIND

Old issue. Resolving as invalid. Context has changed.

> Restore UpgradeTo in order to upgrade a HBase cluster to the latest release
> ---------------------------------------------------------------------------
>
>                 Key: HBASE-11860
>                 URL: https://issues.apache.org/jira/browse/HBASE-11860
>             Project: HBase
>          Issue Type: Improvement
>          Components: HFile, master
>            Reporter: Esteban Gutierrez
>            Assignee: Esteban Gutierrez
>            Priority: Major
>             Fix For: 2.0.0
>
>
> Users should have the option to upgrade to a newer release of HBase without performing a transitive upgrade to HBase 0.96 (EOL'd) or HBase 0.98 and then HBase 1.x or 2.x
> In HBASE-11611 UpgradeTo96 was removed and it won't be possible to migrate a HBase 0.94 cluster to HBase 1.x or 2.x  without the extra step. 
> Initially we can restore part of the functionality of the tool supporting migration to namespaces and report for the existence of any HFileV1 file and ZKDataMigrator could be safely removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)