You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jark Wu (Jira)" <ji...@apache.org> on 2020/06/15 13:05:00 UTC
[jira] [Assigned] (FLINK-18296) Add support for datetype
TIMESTAMP_WITH_LOCAL_ZONE for Json format
[ https://issues.apache.org/jira/browse/FLINK-18296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jark Wu reassigned FLINK-18296:
-------------------------------
Assignee: Shengkai Fang
> Add support for datetype TIMESTAMP_WITH_LOCAL_ZONE for Json format
> ------------------------------------------------------------------
>
> Key: FLINK-18296
> URL: https://issues.apache.org/jira/browse/FLINK-18296
> Project: Flink
> Issue Type: Sub-task
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Affects Versions: 1.11.0
> Reporter: Shengkai Fang
> Assignee: Shengkai Fang
> Priority: Major
>
> Currently we still can't use datatype TIMESTAMP_WITH_LOCAL_ZONE in json format. According to the document descripition of TIMESTAMP_WITH_LOCAL_ZONE, I think the behaviour of this type should work like this when we processing in json :
> # it can read timestamp with timezone in ISO-8601 format or RFC3339 format and transfer timestamp into UTC time or time with user-defined zone for processing;
> # it can output timestamp in format like "yyyy-MM-ddTHH-mm-ss.s\{precision}" or "yyyy-MM-dd HH-mm-ss.s\{precision}"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)