compat: add test for deserializing stringref enabled and disabled#17989
Merged
yaauie merged 1 commit intoelastic:9.0from Sep 4, 2025
Merged
compat: add test for deserializing stringref enabled and disabled#17989yaauie merged 1 commit intoelastic:9.0from
yaauie merged 1 commit intoelastic:9.0from
Conversation
5 tasks
|
💛 Build succeeded, but was flaky
Failed CI Steps |
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
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.





Release notes
[rn: skip]
What does this PR do?
Adds tests to prove that enabling the CBOR stringref extension in #17849 does not create a rollback barrier.
Why is it important/What is the impact to the user?
We want to ensure that a user who has begun using LS 9.x (in which we plan to activate the CBOR stringref extension) can safely roll back to LS 9.0, even if stringref-enabled events are left behind in the PQ.
Checklist
[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files (and/or docker env variables)Related issues