[SPARK-48305][SQL] Add collation support for CurrentLike expressions #46613
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
uros-db
changed the title
uros-db
changed the title
|
@cloud-fan ready for review |
cloud-fan
approved these changes
May 17, 2024
cloud-fan
reviewed
May 17, 2024
sql/core/src/test/scala/org/apache/spark/sql/CollationSQLExpressionsSuite.scala
Outdated
Show resolved
Hide resolved
|
thanks, merging to master! |
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?
Introduce collation awareness for CurrentLike expressions: current_database/current_schema, current_catalog, user/current_user/session_user.
Why are the changes needed?
Add collation support for CurrentLike expressions in Spark.
Does this PR introduce any user-facing change?
Yes, users should now be able to use collated strings within arguments for CurrentLike functions: current_database/current_schema, current_catalog, user/current_user/session_user.
How was this patch tested?
E2e sql tests.
Was this patch authored or co-authored using generative AI tooling?
No.