You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Maxim Gekk (Jira)" <ji...@apache.org> on 2020/03/27 11:38:00 UTC
[jira] [Updated] (SPARK-31286) Specify formats of time zone ID for
JSON/CSV option and from/to_utc_timestamp
[ https://issues.apache.org/jira/browse/SPARK-31286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Gekk updated SPARK-31286:
-------------------------------
Description:
There are two distinct types of ID (see https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html):
# Fixed offsets - a fully resolved offset from UTC/Greenwich, that uses the same offset for all local date-times
# Geographical regions - an area where a specific set of rules for finding the offset from UTC/Greenwich apply
For example three-letter time zone IDs are ambitious, and depend on the locale. They have been already deprecated in JDK, see https://docs.oracle.com/javase/8/docs/api/java/util/TimeZone.html :
{code}
For compatibility with JDK 1.1.x, some other three-letter time zone IDs (such as "PST", "CTT", "AST") are also supported. However, their use is deprecated because the same abbreviation is often used for multiple time zones (for example, "CST" could be U.S. "Central Standard Time" and "China Standard Time"), and the Java platform can then only recognize one of them.
{code}
The ticket aims to specify formats of the `timeZone` option in JSON/CSV datasource, and the `tz` parameter of the from_utc_timestamp() and to_utc_timestamp() functions.
was:
There are two distinct types of ID (see https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html):
# Fixed offsets - a fully resolved offset from UTC/Greenwich, that uses the same offset for all local date-times
# Geographical regions - an area where a specific set of rules for finding the offset from UTC/Greenwich apply
For example three-letter time zone IDs are ambitious, and depend on the locale. They have been already deprecated in JDK, see https://docs.oracle.com/javase/8/docs/api/java/util/TimeZone.html :
{code}
For compatibility with JDK 1.1.x, some other three-letter time zone IDs (such as "PST", "CTT", "AST") are also supported. However, their use is deprecated because the same abbreviation is often used for multiple time zones (for example, "CST" could be U.S. "Central Standard Time" and "China Standard Time"), and the Java platform can then only recognize one of them.
{code}
The ticket aims to specify formats of the SQL config *spark.sql.session.timeZone* in the 2 forms mentioned above.
> Specify formats of time zone ID for JSON/CSV option and from/to_utc_timestamp
> -----------------------------------------------------------------------------
>
> Key: SPARK-31286
> URL: https://issues.apache.org/jira/browse/SPARK-31286
> Project: Spark
> Issue Type: Documentation
> Components: SQL
> Affects Versions: 2.4.5, 3.0.0
> Reporter: Maxim Gekk
> Assignee: Maxim Gekk
> Priority: Major
> Fix For: 3.0.0
>
>
> There are two distinct types of ID (see https://docs.oracle.com/javase/8/docs/api/java/time/ZoneId.html):
> # Fixed offsets - a fully resolved offset from UTC/Greenwich, that uses the same offset for all local date-times
> # Geographical regions - an area where a specific set of rules for finding the offset from UTC/Greenwich apply
> For example three-letter time zone IDs are ambitious, and depend on the locale. They have been already deprecated in JDK, see https://docs.oracle.com/javase/8/docs/api/java/util/TimeZone.html :
> {code}
> For compatibility with JDK 1.1.x, some other three-letter time zone IDs (such as "PST", "CTT", "AST") are also supported. However, their use is deprecated because the same abbreviation is often used for multiple time zones (for example, "CST" could be U.S. "Central Standard Time" and "China Standard Time"), and the Java platform can then only recognize one of them.
> {code}
> The ticket aims to specify formats of the `timeZone` option in JSON/CSV datasource, and the `tz` parameter of the from_utc_timestamp() and to_utc_timestamp() functions.
--
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