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

["Sean Busbey (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-11860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14115266#comment-14115266 ] 

Sean Busbey commented on HBASE-11860:
-------------------------------------

Is your proposal that we adopt a position of always being able to upgrade to a released version from any supported version at the time of release?

e.g. when presumably when 1.0 comes out 0.94 and 0.98 will still be around and you'd like users to be able to go directly to 1.0 from either (and rolling from 0.98?). Similarly current 0.94 users would be able to go directly to 0.98?

Is there already a dev@ discussion around this? Since our [upgrade docs|http://hbase.apache.org/book.html#upgrading] expressly call out not supporting this kind of upgrades it's probably worth preemptively asking for concerns from the wider audience there.

> 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
>             Fix For: 0.99.0, 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
(v6.2#6252)