feat(debeizum): upgrade version of debeizum from 2.4.2 to 2.6.2 #17504
+11
−10
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
KeXiangWang
added
ci/run-backwards-compat-tests
KeXiangWang
force-pushed
the
wkx/update-debeizum-to-2.7.1
branch
from
34d598e
to
75c445a
Compare
KeXiangWang
force-pushed
the
wkx/update-debeizum-to-2.7.1
branch
from
15605b0
to
cefbc89
Compare
|
Waiting for @StrikeW 's review. |
StrikeW
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Due to some fixes/fetures requirements, tentatively upgrade the dependent version of debeizum from
2.4.2.Finalto2.6.2.Final.2.7.0(PR). So I was planning to upgrade to2.7.0.Finaldirectly, which was released on June 27. After testing, it still contains some weird bugs inmysql-cdcsupport. THe error log is here.2.4.2.Finaldoes not support retrieve schema history from upstream sql server automatically. While after2.6.0,recoverysnapshot mode is added to support recovery from empty schema history storage. snapshot.mode. If we keep using2.4.2, we need to find a way to store the schema history, which is non-trivial, making the JVM stateful.Checklist
./risedev check(or alias,./risedev c)Documentation
Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.