-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Fix timestamp to varchar coercer in hive tables #17604
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
Closed
Praveen2112
wants to merge
5
commits into
trinodb:master
from
Praveen2112:praveen/timestamp_string_coercion_fix
Closed
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
4f0aecc
Minor cleanup in OrcTypeTranslator
Praveen2112 0596d32
Cleanup in RcFilePageSourceFactory
Praveen2112 34a105e
For Timestamp to String coercions treat precision as nanoseconds
Praveen2112 c64d36b
fixup! For Timestamp to String coercions treat precision as nanoseconds
Praveen2112 030c40c
Restrict timestamp to varchar coercion for historical dates
Praveen2112 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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -560,14 +560,16 @@ public static List<HiveColumnHandle> toColumnHandles(List<ColumnMapping> regular | |
| projectedColumn.getDereferenceIndices(), | ||
| projectedColumn.getDereferenceNames(), | ||
| fromHiveType, | ||
| fromHiveType.getType(typeManager)); | ||
| // Hive treats TIMESTAMP with NANOSECONDS precision and when we try to coerce from a timestamp column, | ||
| // we read it as TIMESTAMP(9) column and coerce accordingly. | ||
| fromHiveType.getType(typeManager, HiveTimestampPrecision.NANOSECONDS)); | ||
| }); | ||
|
|
||
| return new HiveColumnHandle( | ||
| columnHandle.getBaseColumnName(), | ||
| columnHandle.getBaseHiveColumnIndex(), | ||
| fromHiveTypeBase, | ||
| fromHiveTypeBase.getType(typeManager), | ||
| fromHiveTypeBase.getType(typeManager, HiveTimestampPrecision.NANOSECONDS), | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. (same here)
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we can continue the discussion here - #17604 (comment) |
||
| newColumnProjectionInfo, | ||
| columnHandle.getColumnType(), | ||
| columnHandle.getComment()); | ||
|
|
||
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
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
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
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
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.
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.
what if fromHiveType is a Row/Struct and timestamp field isn't being coerced.
can injecting NANOS leak here?
in fact, i don't know why change here at all
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.
Changing here would allows to read the coerced column as
NANOfrom the underlying file - is there any extension point we could use so as to force the column to be read asNANO?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.
fromHiveType.getType(typeManager)doesn't consider theprecisionfrom the session or config - so aren't we injectingMILLIS- which is mapped toDEFAULTprecision here ?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.
that's why it was deprecated. the code before the changes wasn't good
but i don't know why NANOSECONDS is always good here.
is this applied for coerced columns only?
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.
If we didn't apply
NANOSECONDSthen the data from the underlyingConnectorPageSourceis read asMILLISECONDS- and we can't get aLongTimestampobject from the block - IIUC this applied if the coerced column is a timestamp column, I'll double check for the complex column likeSTRUCT- but without this change we would be leakingMILLI- it is not intentional right ?