[
https://issues.apache.org/jira/browse/FLINK-17752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133982#comment-17133982
]
Jingsong Lee commented on FLINK-17752:
--------------------------------------
Thanks [~jark] for restarting this discussion and summary. Agree with you.
The conversion of {{TIMESTAMP WITH LOCAL TIME ZONE}} looks good to me. This
type is time-zone-domain, so when dealing with string conversion, we must
"correct" the values of other time zones to our local time zone.
Note TIMESTAMP WITHOUT TIME ZONE does not have time zone concept, so whatever
types of string, it just read the "year,month,day" value, so the conversion is
just remove zone information.
I think more popular type is {{TIMESTAMP WITH LOCAL TIME ZONE}} , this one is
more similar to user cases. We should improve it to integration to watermark
and eventtime in 1.12.
> 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)
