From 2cc34df412efbdfce9c77411d144be71962280ce Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?D=C3=A1vid=20Paksy?= Date: Mon, 25 Nov 2024 10:44:58 +0100 Subject: [PATCH 1/2] HBASE-20663 Made sure coprocessor upgrade anchor ID is not duplicated in HBase book - Renamed the anchor ID under "Changes of Note!" section. - Added a link from this section to the other "Upgrading Coprocessors to 2.0" section. - Also fixed the grammar in one of the sentences of the "Coprocessor APIs have changed in HBase 2.0+" section. --- src/main/asciidoc/_chapters/upgrading.adoc | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/src/main/asciidoc/_chapters/upgrading.adoc b/src/main/asciidoc/_chapters/upgrading.adoc index 055acd968078..45c4e71ca9b1 100644 --- a/src/main/asciidoc/_chapters/upgrading.adoc +++ b/src/main/asciidoc/_chapters/upgrading.adoc @@ -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 <>. -[[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+. @@ -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.hfile3.only]] .HBase 2.0+ can no longer write HFile v2 files. From fc1da60fd17ba759ae61af1074f05ff224fe8851 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?D=C3=A1vid=20Paksy?= Date: Mon, 25 Nov 2024 13:20:53 +0100 Subject: [PATCH 2/2] HBASE-20663 Fixed bc.deploy.modes broken anchor ID Fixed the anchor ID of "BucketCache Deploy Modes". This way a broken link is now fixed. --- src/main/asciidoc/_chapters/architecture.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/asciidoc/_chapters/architecture.adoc b/src/main/asciidoc/_chapters/architecture.adoc index 08f353972468..3a380ed68105 100644 --- a/src/main/asciidoc/_chapters/architecture.adoc +++ b/src/main/asciidoc/_chapters/architecture.adoc @@ -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.