Repository navigation
Conversation
uros-db
changed the title
mkaravel
reviewed
May 16, 2024
mkaravel
approved these changes
May 20, 2024
mkaravel
left a comment
mkaravel
left a comment
Contributor
There was a problem hiding this comment.
Thank you for addressing my comments.
LGTM!
Contributor
|
Please update the PR description. |
uros-db
changed the title
uros-db
commented
May 21, 2024
uros-db
left a comment
uros-db
left a comment
Contributor
Author
There was a problem hiding this comment.
updated PR description & title
@cloud-fan ready for review
Contributor
dbatomic
approved these changes
May 28, 2024
Contributor
|
please fix merge conflicts. |
Contributor
|
thanks, merging to master! |
cloud-fan
pushed a commit
that referenced
this pull request
Jun 11, 2024
### What changes were proposed in this pull request? Renaming `UTF8_BINARY_LCASE` collation to `UTF8_LCASE`. ### Why are the changes needed? As part of the collation effort in Spark, we've moved away from byte-by-byte logic towards character-by-character logic, so what we used to call `UTF8_BINARY_LCASE` is now more precisely `UTF8_LCASE`. For example, string searching in UTF8_LCASE now works on character-level (rather than on byte-level), which is reflected in this PRs: #46511, #46589, #46682, #46761, #46762. In addition, string comparison also works on character-level now, as per the changes introduced in this PR: #46700. ### Does this PR introduce _any_ user-facing change? Yes, what was previously named `UTF8_BINARY_LCASE` collation, will from now on be named `UTF8_LCASE`. ### How was this patch tested? Existing tests. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #46924 from uros-db/rename-lcase. Authored-by: Uros Bojanic <157381213+uros-db@users.noreply.github.com> Signed-off-by: Wenchen Fan <wenchen@databricks.com>
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
4 participants
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?
String searching in UTF8_BINARY_LCASE now works on character-level, rather than on byte-level. For example:
instr("İ", "i"); now returns 0, because there exists nostart, lensuch thatlowercase(substring("İ", start, len)) == "i".Why are the changes needed?
Fix functions that give unusable results due to one-to-many case mapping when performing string search under UTF8_BINARY_LCASE (see example above).
Does this PR introduce any user-facing change?
Yes, behaviour of
instrandsubstring_indexexpressions is changed for edge cases with one-to-many case mapping.How was this patch tested?
New unit tests in
CollationSupportSuite.Was this patch authored or co-authored using generative AI tooling?
No.