You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2021/02/17 12:20:00 UTC

[jira] [Commented] (SPARK-34451) Add alternatives for datetime rebasing SQL configs and deprecate legacy configs

    [ https://issues.apache.org/jira/browse/SPARK-34451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17285804#comment-17285804 ] 

Apache Spark commented on SPARK-34451:
--------------------------------------

User 'MaxGekk' has created a pull request for this issue:
https://github.com/apache/spark/pull/31576

> Add alternatives for datetime rebasing SQL configs and deprecate legacy configs
> -------------------------------------------------------------------------------
>
>                 Key: SPARK-34451
>                 URL: https://issues.apache.org/jira/browse/SPARK-34451
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 3.2.0
>            Reporter: Maxim Gekk
>            Priority: Major
>
> The rebasing SQL configs like spark.sql.legacy.parquet.datetimeRebaseModeInRead can be used not only for migration from previous Spark versions but also to read/write datatime columns saved by other systems/frameworks/libs. The ticket aims to move the configs from the legacy namespace by introducing alternatives (like spark.sql.parquet.datetimeRebaseModeInRead) and deprecating the legacy configs (spark.sql.legacy.parquet.datetimeRebaseModeInRead).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org