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.
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
Support CPU path for from_utc_timestamp function with timezone #9689
Support CPU path for from_utc_timestamp function with timezone #9689
Changes from 5 commits
9e67c79
69cb0fe
c420ccf
c9932a1
000868a
74d760b
50c1c72
5497df5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The internal Spark config should actually be wired into here. The logic should be:
If the timezone is UTC -> Always stay on the GPU (no-op)
If the timezone is not UTC -> if the config is set to true, use the CPU POC as long as the timezone is supported, otherwise fallback to CPU
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.
Internal Spark config (
spark.rapids.test.CPU.timezone
) was wired inside isSupportedTimezone method.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.
I still think it's better to wire the config directly here. I find that putting it in the logic of isSupportedTimezone a bit confusing to understand, even though it might make the migration process simpler in a way. It's not actually hard to remove the config when we migrate to GPU timezone DB. Plus I'm not sure depending on the review if that will make it in 23.12, so I think we should stay safe with this code path.
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.
Updated. Please take a further look.