Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.0.0-alpha-1, 2.2.0, 2.3.0
-
None
-
None
Description
While evaluating interface compatibilities for 2.3.0RC0, I noticed the deprecation comment for o.a.h.h.tool.LoadIncrementalHFiles says
* @deprecated since 2.2.0, will be removed in 3.0.0. Use {@link BulkLoadHFiles} instead.
This is contrary to an explicit example in our book, which states:
An API needs to be deprecated for a whole major version before we will change/remove it.
An example: An API was deprecated in 2.0.1 and will be marked for deletion in 4.0.0. On the other hand, an API deprecated in 2.0.0 can be removed in 3.0.0.
Maybe there are other comments like this, which need addressed. We should grep the codebase and make appropriate adjustments.