You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nick Dimiduk (Jira)" <ji...@apache.org> on 2020/06/22 16:06:00 UTC
[jira] [Created] (HBASE-24614) o.a.h.h.tool.LoadIncrementalHFiles
deprecation comment does not span an entire release
Nick Dimiduk created HBASE-24614:
------------------------------------
Summary: o.a.h.h.tool.LoadIncrementalHFiles deprecation comment does not span an entire release
Key: HBASE-24614
URL: https://issues.apache.org/jira/browse/HBASE-24614
Project: HBase
Issue Type: Task
Components: community
Affects Versions: 2.2.0, 3.0.0-alpha-1, 2.3.0
Reporter: Nick Dimiduk
While evaluating interface compatibilities for 2.3.0RC0, I noticed the deprecation comment for {{o.a.h.h.tool.LoadIncrementalHFiles}} says
{noformat}
* @deprecated since 2.2.0, will be removed in 3.0.0. Use {@link BulkLoadHFiles} instead. {noformat}
This is contrary to an explicit example in our [book|https://hbase.apache.org/book.html#hbase.versioning], which states:
{quote}
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.
{quote}
Maybe there are other comments like this, which need addressed. We should grep the codebase and make appropriate adjustments.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)