-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
br: avoid too many warning logs after update schema version (#43416) #43619
br: avoid too many warning logs after update schema version (#43416) #43619
Conversation
Signed-off-by: Leavrth <jianjun.liao@outlook.com>
Signed-off-by: Leavrth <jianjun.liao@outlook.com>
Signed-off-by: Leavrth <jianjun.liao@outlook.com>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 55dd2c9
|
/retest |
2 similar comments
/retest |
/retest |
This is an automated cherry-pick of #43416
What problem does this PR solve?
Issue Number: close #43402
Problem Summary:
after log restore, there are many warning logs, see the issue.
What is changed and how it works?
Add a diffKey whose
regenerateSchemaMap
is true to trigger full load schemas.Check List
Tests
If modify the
64 + ...
to6
to triggerloadSchemaDiff
, the log would print that as follows:Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.