[
https://issues.apache.org/jira/browse/FLINK-17752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17134164#comment-17134164
]
Jark Wu commented on FLINK-17752:
---------------------------------
Hi [~twalthr], I can see your points. I'm also fine to have a strict
interpreting. To summary the result, for {{TIMESTAMP WITHOUT TIME ZONE}}, if
the {{timestamp-format}} is {{"SQL"}}, then parsed and generated value is
always "2020-06-12 11:46:22.123456789" (without "T" and time zone). If the
{{timestamp-format}} is {{"ISO-8601"}}, then the parsed and generated value is
always "2020-06-12T11:46:22.123456789" (with "T" and without time zone). Other
formats are not supported for {{TIMESTAMP WITHOUT TIME ZONE}}. {{"ISO-8601"}}
and {{"RFC-3339"}} are both supported for {{TIMESTAMP WITH LOCAL TIME ZONE}},
but requires the value with "Z" suffix. Does that make sense to you?
> Align the timestamp format with Flink SQL types in JSON format
> --------------------------------------------------------------
>
> Key: FLINK-17752
> URL: https://issues.apache.org/jira/browse/FLINK-17752
> Project: Flink
> Issue Type: Bug
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile), Table
> SQL / Ecosystem
> Reporter: Jark Wu
> Assignee: Shengkai Fang
> Priority: Critical
> Fix For: 1.11.0
>
>
> Currently, we are using RFC3339_TIMESTAMP_FORMAT (which will add timezone at
> the end of string) to as the timestamp format in JSON. However, the string
> representation fo {{TIMESTAMP (WITHOUT TIME ZONE)}} shoudn't adding 'Z' at
> the end.
> Other discussions:
> [1]:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/TIME-TIMESTAMP-parse-in-Flink-TABLE-SQL-API-td33061.html
> [2]:
> http://apache-flink.147419.n8.nabble.com/json-timestamp-json-flink-sql-td1914.html
> [3]: http://apache-flink.147419.n8.nabble.com/FLINK-SQL-td2074.html
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
