Fix schema mismatch w/Parquet INT64 & Timestamp#13857
Merged
arhimondr merged 1 commit intoprestodb:masterfrom Dec 12, 2019
Merged
Fix schema mismatch w/Parquet INT64 & Timestamp#13857arhimondr merged 1 commit intoprestodb:masterfrom
arhimondr merged 1 commit intoprestodb:masterfrom
Conversation
arhimondr
approved these changes
Dec 12, 2019
Contributor
Author
|
@arhimondr Does this not go far enough? Should all the other timestamp types that inherit from abstract long type work as well? |
Member
|
@aweisberg You mean the Timestamp With Time Zone? |
Contributor
Author
|
Turns out Hive only supports Timestamp so no further changes were required. |
7 tasks
6 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Schema checks are too strict and prevent timestamp type from being read as int64 from Parquet files.
Fixes: #13855