Skip to content

HBASE-20663 Make sure coprocessor upgrade anchor ID is not duplicated in HBase book #6493

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Apache9 merged 2 commits into from
Dec 8, 2024
+3 −5
Merged

HBASE-20663 Make sure coprocessor upgrade anchor ID is not duplicated in HBase book #6493

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2cc34df
HBASE-20663 Made sure coprocessor upgrade anchor ID is not duplicated…
PDavid Nov 25, 2024
fc1da60
HBASE-20663 Fixed bc.deploy.modes broken anchor ID
PDavid Nov 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/main/asciidoc/_chapters/architecture.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1148,7 +1148,7 @@ benefit of NOT provoking GC.
From HBase 2.0.0 onwards, the notions of L1 and L2 have been deprecated. When BucketCache is turned on, the DATA blocks will always go to BucketCache and INDEX/BLOOM blocks go to on heap LRUBlockCache. `cacheDataInL1` support has been removed.
====

[[bc.deloy.modes]]
[[bc.deploy.modes]]
====== BucketCache Deploy Modes
The BucketCache Block Cache can be deployed _offheap_, _file_ or _mmaped_ file mode.

Expand Down
6 changes: 2 additions & 4 deletions src/main/asciidoc/_chapters/upgrading.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -601,7 +601,7 @@ The HBase shell command relies on a bundled JRuby instance. This bundled JRuby b

The HBase shell command now ignores the '--return-values' flag that was present in early HBase 1.4 releases. Instead the shell always behaves as though that flag were passed. If you wish to avoid having expression results printed in the console you should alter your IRB configuration as noted in the section <<irbrc>>.

[[upgrade2.0.coprocessors]]
[[upgrade2.0.coprocessors-changes]]
.Coprocessor APIs have changed in HBase 2.0+

All Coprocessor APIs have been refactored to improve supportability around binary API compatibility for future versions of HBase. If you or applications you rely on have custom HBase coprocessors, you should read link:https://issues.apache.org/jira/browse/HBASE-18169[the release notes for HBASE-18169] for details of changes you will need to make prior to upgrading to HBase 2.0+.
Expand All @@ -618,9 +618,7 @@ For example, if you had a BaseRegionObserver in HBase 1.2 then at a minimum you
...
----

////
This would be a good place to link to a coprocessor migration guide
////
For more information, see <<upgrade2.0.coprocessors,Upgrading Coprocessors to 2.0>>.

[[upgrade2.0.hfile3.only]]
.HBase 2.0+ can no longer write HFile v2 files.
Expand Down