Be more defensive when parsing shortstr values in tables - #2064
Merged
Conversation
Contributor
Author
|
@Mergifyio backport |
❌ No backport have been createdDetails
GitHub error: |
Contributor
Author
|
@Mergifyio backport v5.x |
✅ Backports have been createdDetails
|
michaelklishin
added a commit
that referenced
this pull request
Aug 27, 2026
Be more defensive when parsing shortstr values in tables (backport #2064)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Note: this enforces the AMQP 0-9-1 255 byte limit on short strings.
We can consider bumping it a bit to reduce the risk of this being a minor breaking change.
In any case, the 255 byte limit has been around for as long as the protocol and RabbitMQ has (19-20 years depending on how you count), just not necessarily universally enforced.