-
Notifications
You must be signed in to change notification settings - Fork 336
fix: gate non-default collations for Spark 4 datetime expressions #4693
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
Open
0lai0
wants to merge
6
commits into
apache:main
Choose a base branch
from
0lai0:fix-4646-Gate-StringTypeWithCollation
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
d709aa0
Gate non-default collations for Spark 4 datetime expressions
0lai0 1862d75
Merge branch 'main' into fix-4646-Gate-StringTypeWithCollation
0lai0 5f59edb
Gate datetime collation incompatibility reasons by Spark version
0lai0 aa36154
Merge branch 'main' into fix-4646-Gate-StringTypeWithCollation
0lai0 fde532e
Merge branch 'main' into fix-4646-Gate-StringTypeWithCollation
0lai0 6671fcf
regression coverage in CometCollationSuite
0lai0 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
This seems incorrect, or is at least inconsistent with other date/time functions. It seems there is no way to enable the native incompatible expression now due to the
hasNonDefaultStringCollationcheck introduced here?PR looks good other than this issue.
Uh oh!
There was an error while loading. Please reload this page.
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.
Thanks for catching this!!
I missed it. The collation check in
canUseNativewas incorrectly blocking the native path even whenDateFormatClass.allowIncompatible=true.I removed the guard so that the non-default collation case is now handled by
getSupportLevel()as Incompatible. WhenallowIncompatibleis false, the request still routes through the dispatcher/fallback, but when it is true, the native path can be used.I have also added regression coverage in
CometCollationSuitefor Spark 4.0 and 4.1 to handle cases involvingdate_formatwith a collated literal format andDateFormatClass.allowIncompatible=true.