[ https://issues.apache.org/jira/browse/SPARK-27528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-27528. ---------------------------------- Resolution: Fixed Fix Version/s: 3.0.0 Issue resolved by pull request 24425 [https://github.com/apache/spark/pull/24425] > Use Parquet logical type TIMESTAMP_MICROS by default > ---------------------------------------------------- > > Key: SPARK-27528 > URL: https://issues.apache.org/jira/browse/SPARK-27528 > Project: Spark > Issue Type: Improvement > Components: SQL > Affects Versions: 2.4.1 > Reporter: Maxim Gekk > Assignee: Maxim Gekk > Priority: Minor > Fix For: 3.0.0 > > > Currently, Spark uses INT96 type for timestamps written to parquet files. To > store Catalyst's Timestamp values as INT96, Spark converts microseconds since > epoch to nanoseconds in Julian calendar. This conversion is not necessary if > Spark saves timestamps as Parquet TIMESTAMP_MICROS logical type. The ticket > aims to switch on TIMESTAMP_MICROS from INT96 in write by default. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org