fix: fix orc read timestamp under debian #43
Merged
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.
Purpose
Linked issue: #42
We recently received a user report that, on Debian systems, reading timestamp data from the same ORC file yields different results compared to Ubuntu systems. Through debugging, we found that if the timezone recorded in the ORC file's footer is not GMT and the timestamp is earlier than 1900-12-31 15:54:17, Debian and Ubuntu systems produce different results. To address this, we have updated our dataset to ensure all ORC files use GMT as their timezone. Additionally, we have explicitly set the timezone to GMT in both the ORC reader and writer.
Tests
ScanInteTest/ReadInteTest