You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 70296a2
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: src/main/asciidoc/_chapters/upgrading.adoc
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,8 @@ In addition to the usual API versioning considerations HBase has other compatibi
67
67
68
68
.Client API compatibility
69
69
* Allow changing or removing existing client APIs.
70
-
* An API needs to be deprecated for a major version before we will change/remove it.
70
+
* An API needs to be deprecated for a whole major version before we will change/remove it.
71
+
** 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.
71
72
* APIs available in a patch version will be available in all later patch versions. However, new APIs may be added which will not be available in earlier patch versions.
72
73
* New APIs introduced in a patch version will only be added in a source compatible way footnote:[See 'Source Compatibility' https://blogs.oracle.com/darcy/entry/kinds_of_compatibility]: i.e. code that implements public APIs will continue to compile.
73
74
** Example: A user using a newly deprecated API does not need to modify application code with HBase API calls until the next major version.
0 commit comments