[branch-2.7] Upgrade the BookKeeper version to 4.12.1 #16775
Merged
+42
−42
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
When running
bin/bookkeeper shell cookie_update
command, we get the following exception.The reason is that in BookKeeper 4.12.0, it depends on the
com.beust. commander
version1.48
, however, in Pulsar, we depend on thecom.beust. commander
version1.78
. The Pulsar depends version overrides the BookKeeper's depends version.However,
com.beust. commander
1.78 version's interface has been changed, which leads to the BookKeeper shell command can't be executed.In BookKeeper 4.12.1, it upgrades the
com.beust. commander
version to 1.78 in apache/bookkeeper#2523. So we can upgrade BookKeeper dependency from 4.12.0 to 4.12.1 to solve this bug.Modification
Upgrade the BookKeeper version from 4.12.0 to 4.12.1
Documentation
Check the box below or label this PR directly.
Need to update docs?
doc-required
(Your PR needs to update docs and you will update later)
doc-not-needed
(Please explain why)
doc
(Your PR contains doc changes)
doc-complete
(Docs have been already added)