Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0.0
-
None
-
None
Description
Feedback from mdrob on HBASE-19158:
Classes/Methods moved:
HBASE-19425(and subtasks) Put/Delete/Increment/AppendHBASE-19627(and subtasks) Cell & ImplHBASE-18978(and subtasks) Async/TableHBASE-18805(and subtasks) Async/AdminHBASE-14996(and subtasks) Lots of misc changesHBASE-13197(and subtasks) ConnectionHBASE-13844KeyValue -> CellUtil- Maybe
HBASE-19950is worth calling out? Not really an upgrade issue though, but I know the old behavior of SCVF changed in a surprising way for the YARN ATS folks, when they were previously relying on what ended up being a bug.Could be mitigated by having a compatibility report, but would benefit from narrative messaging.
Almost definitely need a blanket reminder that some deprecated APIs went away.
from @busbey on HBASE-19158
* Classes/Methods moved:
* Almost definitely need a blanket reminder that some deprecated APIs went away.
My intention was for both of these to be handled by this blurb:
+[[upgrade2.0.public.api]] +.Multiple breaking changes to source and binary compatibility for client API +The Java client API for HBase has a number of changes that break both source and binary compatibility for details see the Compatibility Check Report for the release you'll be upgrading to. + +<!-- This would be a good place to link to an appendix on migrating applications --> +I figure once we get an appendix that provides guidance on migrating an application from 1.x to 2.x we can also link to it.
Get an appendix in place and then update the upgrade section as needed to draw attention to it.