[SPARK-48283][SQL] Modify string comparison for UTF8_BINARY_LCASE#46700
Closed
uros-db wants to merge 16 commits into
Closed
[SPARK-48283][SQL] Modify string comparison for UTF8_BINARY_LCASE#46700uros-db wants to merge 16 commits into
uros-db wants to merge 16 commits into
Conversation
mkaravel
reviewed
May 24, 2024
dbatomic
reviewed
Jun 4, 2024
mkaravel
reviewed
Jun 6, 2024
Contributor
mkaravel
left a comment
There was a problem hiding this comment.
Main question here is whether we want to fix the "conversion" from UTF8String to Java string in this PR or in a follow up PR (see comments in the PR). Either way is fine with me. By "conversion" here I mean:
- Splitting the UTF8String value into illegal and legal UTF8 byte sequences as per UNICODE (no surrogate semantics).
- Replacing illegal byte sequences with U+FFFD.
mkaravel
approved these changes
Jun 6, 2024
Contributor
Author
|
in conclusion: we'll need to modify the logic for illegal UTF8 byte sequence replacement, to stay consistent with ICU4C however, we'll do this in a follow-up PR |
Contributor
Author
|
@cloud-fan please review |
cloud-fan
approved these changes
Jun 6, 2024
Contributor
|
thanks, merging to master! |
This was referenced Jun 10, 2024
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 comparison and hashing in UTF8_BINARY_LCASE is now context-unaware, and uses ICU root locale rules to convert string to lowercase at code point level, taking into consideration special cases for one-to-many case mapping. For example: comparing "ΘΑΛΑΣΣΙΝΟΣ" and "θαλασσινοσ" under UTF8_BINARY_LCASE now returns true, because Greek final sigma is special-cased in the new comparison implementation.
Why are the changes needed?
Does this PR introduce any user-facing change?
Yes, comparing strings under UTF8_BINARY_LCASE will now give different results in two kinds of special cases (Turkish dotted letter "i" and Greek final letter "sigma").
How was this patch tested?
Unit tests in
CollationSupportSuite.Was this patch authored or co-authored using generative AI tooling?
No.