-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-48284][SQL] Fix UTF8String indexOf behaviour for empty string search #46581
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
MaxGekk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@uros-db Is the changes still valid?
uros-db
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
@uros-db Is the test failure related to your PR? |
|
yes, those tests likely need to be updated in order for this PR to pass however, I'm not sure that we want to proceed with this at this time |
|
We're closing this PR because it hasn't been updated in a while. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
What changes were proposed in this pull request?
Currently, UTF8String.indexOf returns 0 when given an empty parameters string, and any integer start value. Examples:
This is not correct, as "start" is not taken into consideration. Correct behaviour would be:
Why are the changes needed?
Fix a bug in
indexOfimplementation.Does this PR introduce any user-facing change?
Yes,
indexOfbehaves differently with empty patterns.How was this patch tested?
New unit tests.
Was this patch authored or co-authored using generative AI tooling?
No.