Just FYI. Tracking this in < https://issues.apache.org/jira/browse/HBASE-14193>
On Sat, Aug 1, 2015 at 2:05 AM, Lars Francke <[email protected]> wrote: > Great, thanks Lars. I'll go ahead and will try to clean this up then. > > On Fri, Jul 31, 2015 at 4:33 PM, lars hofhansl <[email protected]> wrote: > >> Following our guidelines as stated here: >> https://hbase.apache.org/book.html#hbase.versioning we can remove the >> upgrade path from 2.0.Considering the 0.98 is a major version step over >> 0.94 we could in theory remove such from 1.x, but we only established >> semantic versioning with 1.0.0. >> So, yes, it seems we can (and I would argue, should) remove the upgrade >> code in question from 2.x. >> -- Lars >> >> From: Lars Francke <[email protected]> >> To: [email protected] >> Sent: Friday, July 31, 2015 3:59 AM >> Subject: Support for upgrades from 0.94 >> >> Hi, >> >> this is referring to these two issues: >> <https://issues.apache.org/jira/browse/HBASE-8778> >> <https://issues.apache.org/jira/browse/HBASE-11611> >> >> I'm still looking for deprecated stuff that can be cleaned up. We have a >> file in the code (FSTableDescriptorMigrationToSubdir) that is used to >> migrate pre-0.96 table format to the new version. It has an annotation >> that >> marks it as to-delete for the next major version after 0.96. >> >> HBASE-11611 removed the class UpgradeTo96 without removing the hbase shell >> command "upgrade" which referred to that class. So that means that as of >> 2.0.0 upgrades from 0.94 are not supported anymore (If I understand that >> correctly). >> >> Are we okay with that? If so I'd like to create a JIRA removing the >> remnants and documenting this. >> >> Otherwise we need to partially revert HBASE-11611 and probably adapt the >> Upgrade class. >> >> Cheers, >> Lars >> >> >> >> > >
