Fix MatchOperator class structure and serialization code for 8.x #120836
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
carlosdelest
added
auto-backport
|
Fixed by not serializing MatchOperator in #120360. |
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.
#120504 introduced a serialization bug for
MatchOperator.readFromandwriteToare not symmetric, and this causes bwc test errors in main for #120360.Also, the main goal of extracting an
AbstractMatchFullTextFunctionwas to makeMatchandMatchOperatorto inherit from it. MatchOperator did not do so, and this is corrected as well on this PR.This PR solves both issues first in 8.x, and will be backported to main to ensure bwc tests can pass.