[
https://issues.apache.org/jira/browse/PARQUET-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16598521#comment-16598521
]
ASF GitHub Bot commented on PARQUET-1388:
-----------------------------------------
nandorKollar opened a new pull request #519: PARQUET-1388: Nanosecond precision
time and timestamp - parquet-mr
URL: https://github.com/apache/parquet-mr/pull/519
This PR introduces nanosecond precision time and timestamp types to
parquet-mr. It depends on https://github.com/apache/parquet-format/pull/102,
should be committed once this format change is released.
Nanosecond precision is introduced only into the new logical type API, the
old version (ConvertedType in format and OriginalType in mr) doesn't have a
corresponding enum value for nanoseconds. Therefore in the Thrift schema these
fields will be null, only new releases can interpret nanosecond precision,
older readers can only see the physical type.
In addition to nanosecond precision, I also refactored the modules to use
the new logical type API for internal decisions (e.g.: replaced the
OriginalType-based switch cases, for example in type builder when checking if
the proper annotation is present on physical type). This part (
commit with title: Refactor modules to use the new logical type API) doesn't
need new format release, and can be split out from this PR if needed.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Nanosecond precision time and timestamp - parquet-mr
> ----------------------------------------------------
>
> Key: PARQUET-1388
> URL: https://issues.apache.org/jira/browse/PARQUET-1388
> Project: Parquet
> Issue Type: Improvement
> Components: parquet-mr
> Reporter: Nandor Kollar
> Priority: Major
> Labels: pull-request-available
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
