[
https://issues.apache.org/jira/browse/FLINK-17752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17108950#comment-17108950
]
Dawid Wysakowicz commented on FLINK-17752:
------------------------------------------
Just to add a few more issues with time handling in json format:
* TIMESTAMP(_WITHOUT_TIME_ZONE) - has a LocalDateTime semantics, you can not
map it to a single point in time, now it prints in UTC with 'Z' suffix
* TIME_WITHOUT_TIME_ZONE - the same problem as above, sql says no time zone
information
* TIMESTAMP_WITH_TIME_ZONE - (we do not support this type yet in the planner,
so not a big problem) - it always prints it in UTC (with 'Z' suffix), even
though it should print its time zone
* there is no support for TIME_WITH_LOCAL_TIME_ZONE - this could use the
current format, it has an Instant semantics which means it points to a
particular moment in time, the way we represent it is up to us (printing date
time in utc or long since epoch utc)
> 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: Sub-task
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Reporter: Jark Wu
> Priority: Major
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
