RMQ-1263: An attempt to make shovel status tuple handling backwards compatible #13628
Conversation
This file contains hidden or 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
ikavgo
requested review from
michaelklishin
and removed request for
michaelklishin
mergify bot
pushed a commit
that referenced
this pull request
Mar 26, 2025
(cherry picked from commit 03526b5)
michaelklishin
added a commit
that referenced
this pull request
Mar 27, 2025
RMQ-1263: An attempt to make shovel status tuple handling backwards compatible (backport #13628)
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.
This is a followup for #13620. For cluster upgrades/mixed versions we want shovel commands and management status formatter to be backwards compatible. I hope I got it right :-)
PS. CrashCounter goes off for shovel_management even on main branch for me.