-
Notifications
You must be signed in to change notification settings - Fork 289
Support DST timezones conversion for ORC #14544
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
res-life
wants to merge
13
commits into
NVIDIA:main
Choose a base branch
from
res-life:orc-tz
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 all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
183176d
Support DST timezones for ORC
3e4fca1
Update tests
181c5e7
Update tests
c969c75
Update tests
688e7b4
Use a fixed random seed in OrcTimezoneSuite
0627492
Use a unique tmp dir in OrcTimezonePerfSuite
7427a61
Normalize legacy ORC writer timezone IDs before ZoneId.of
7fdf1e4
Compare ORC stripe writer timezones by rule-equivalence
1a77757
Cover legacy/alias timezone IDs in OrcTimezoneSuite
1b17fe5
Add explicit FileUtils import in OrcTimezonePerfSuite
res-life ebabd91
Fix comment
81b3375
Compare ORC writer timezones by rule-equivalence in multi-file split …
0928caa
Compare ORC writer/reader timezones via ZoneId rules, not TimeZone
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
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.
Why delete the comments that explain why we are setting the start and end timestamp to what they are? Have we tested outside of this range recently? Do we have a follow on issue to fix the range limitations?