[SPARK-31672][SQL] Fix loading of timestamps before 1582-10-15 from dictionary encoded Parquet columns #28489
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?
Modified the
decodeDictionaryIds()
method ofVectorizedColumnReader
to handle especiallyTimestampType
when the passed parameterrebaseDateTime
is true. In that case, decoded milliseconds/microseconds are rebased from the hybrid calendar to Proleptic Gregorian calendar usingRebaseDateTime
.rebaseJulianToGregorianMicros()
.Why are the changes needed?
This fixes the bug of loading timestamps before the cutover day from dictionary encoded column in parquet files. The code below forces dictionary encoding:
Load the dates back:
Expected values must be 1001-01-01 01:02:03.123 but not 1001-01-07 00:32:20.123.
Does this PR introduce any user-facing change?
Yes. After the changes:
How was this patch tested?
Modified the test
SPARK-31159: rebasing timestamps in write
inParquetIOSuite
to checked reading dictionary encoded dates.