[
https://issues.apache.org/jira/browse/FLINK-17752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306942#comment-17306942
]
jiamo commented on FLINK-17752:
-------------------------------
Why not offer format in
[https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html.|https://docs.oracle.com/javase/8/docs/api/java/time/format/DateTimeFormatter.html]
Only have SQL and ISO-8601 and still don't support the total stand (such like
2021-03-23T09:04:37+00:00 ). The another CAST after string was useless (but now
was must!).
We can let user input what the format they want.
> 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
>
> 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)
