You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Shengkai Fang (Jira)" <ji...@apache.org> on 2020/07/29 03:34:00 UTC
[jira] [Commented] (FLINK-18747) Make Debezium Json format support
timestamp with timezone
[ https://issues.apache.org/jira/browse/FLINK-18747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166839#comment-17166839 ]
Shengkai Fang commented on FLINK-18747:
---------------------------------------
Currently, we have implemented TIMESTAMP_WITH_LOCAL_ZONE datatype to support timestamp with zone in FLINK-18296.
> Make Debezium Json format support timestamp with timezone
> ---------------------------------------------------------
>
> Key: FLINK-18747
> URL: https://issues.apache.org/jira/browse/FLINK-18747
> Project: Flink
> Issue Type: Improvement
> Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
> Reporter: Leon Hao
> Priority: Major
>
> Debezium Connector for MySQL maps timestamp datatype to ISO 8601 with time zone format like '2020-07-29T01:09:52.534173Z'. Current code doesn't support the timestamp with time zone even if we set 'debezium-json.timestamp-format.standard' = 'ISO-8601'. I think we should support it because:
> 1. ISO-8601 itself supports timestamp with timezone.
> 2. Sometimes we need to CDC many tables with many timestamp fields from Mysql. It would be a waste of time to convert these fields from string to timestamp manually as proposed by this post FLINK-17752
> 3. It is very confusing to users when errors occur although the document says Flink supports debezium json format and ISO-8601.
> I think we can create a new debezium-json.timestamp-format option to support timestamp with time zone or have a better documentation letting users know Flink dose not support it.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)