Skip to content

Conversation

@omalley
Copy link
Contributor

@omalley omalley commented Aug 23, 2019

This PR changes the representation in TimestampColumnVector, which has two fields time (millis since 1970) and nanos (nanos within seconds). The problem came because the last 3 digits of time and top 3 digits of nanos both represent the millis. Before ORC-306, the last 3 digits of time were always 0. This patch restores that behavior.

@omalley omalley closed this in f936740 Aug 26, 2019
@omalley omalley merged commit f936740 into apache:master Aug 26, 2019
omalley added a commit that referenced this pull request Aug 26, 2019
This caused SPARK-27594.

Fixes #420

Signed-off-by: Owen O'Malley <[email protected]>
omalley added a commit that referenced this pull request Aug 26, 2019
This caused SPARK-27594.

Fixes #420

Signed-off-by: Owen O'Malley <[email protected]>
rdsr pushed a commit to linkedin/iceberg that referenced this pull request Sep 10, 2019
* Remove workaround on timestamp nanos as per ORC-546:
apache/orc#420

* Use ORC TypeDescription attributes for column mapping

(cherry picked from commit 1b50f282403b281b1d09980c17a659ba6c46f5d9)
rdsr pushed a commit to linkedin/iceberg that referenced this pull request Sep 24, 2019
* Remove workaround on timestamp nanos as per ORC-546:
apache/orc#420

* Use ORC TypeDescription attributes for column mapping

(cherry picked from commit 1b50f282403b281b1d09980c17a659ba6c46f5d9)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants