-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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.
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
[improve][branch-2.10]upgrade the bookkeeper version to 4.14.7 #19179
Conversation
@horizonzy Please add the following content to your PR description and select a checkbox:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you should update the license file as well
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please hold on to the upgrade due to the RocksDB issue. apache/bookkeeper#3734
The pr had no activity for 30 days, mark with Stale label. |
BookKeeper 4.14.7 has been released, we can use BookKeeper 4.14.7 directly. |
9cd5c66
to
5bad78b
Compare
9322695
to
2289c03
Compare
@horizonzy The OWASP check was failed. Could you please merge branch-2.10 to fix it? |
@liangyepianzhou If the master has resolved the OWASP check, I think we can merge this PR directly. Because the CI need to rerun a few times before getting passed. |
Fixes #xyz
Master Issue: #xyz
PIP: #xyz
Motivation
Motivation
BookKeeper 4.14.7 has been released and it contains a lot of notable bug fixes. We need to upgrade the BookKeeper dependency from 4.14.5 to 4.14.7.
BookKeeper release notes can be found:
https://github.com/apache/bookkeeper/releases
Modifications
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes
Documentation
doc
doc-required
doc-not-needed
doc-complete
Matching PR in forked repository
PR in forked repository: