[SPARK-59063][SQL] Use byte-length guard in LikeSimplification - #58374
Open
marcuslin123 wants to merge 1 commit into
Open
[SPARK-59063][SQL] Use byte-length guard in LikeSimplification#58374marcuslin123 wants to merge 1 commit into
marcuslin123 wants to merge 1 commit into
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
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.
What changes were proposed in this pull request?
This PR changes the
prefix%suffixbranch ofLikeSimplificationto useOctetLengthwith the UTF-8 byte lengths of the prefix and suffix. It alsoupdates the optimizer plan tests and adds SPARK-59063 coverage for multibyte
UTF-8 characters.
Why are the changes needed?
Lengthscans every input string to count code points.OctetLengthreads thestored UTF-8 byte length in constant time, while the existing
StartsWithandEndsWithpredicates continue to enforce the pattern boundaries.Does this PR introduce any user-facing change?
No.
How was this patch tested?
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Codex (GPT-5) for code assistance.