[ https://issues.apache.org/jira/browse/FLINK-27018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522793#comment-17522793 ]
jeff-zou commented on FLINK-27018: ---------------------------------- I think it's better to be consistent in converting, because many scenarios require equals, For example, After I sinked the result to ES, I need to use the original value to find out if the result exsits. > timestamp missing end zero when outputing to kafka > --------------------------------------------------- > > Key: FLINK-27018 > URL: https://issues.apache.org/jira/browse/FLINK-27018 > Project: Flink > Issue Type: Bug > Components: Connectors / Kafka > Affects Versions: 1.13.5 > Reporter: jeff-zou > Priority: Major > Attachments: kafka.png > > > the bug is described as follows: > > {code:java} > data in source: > 2022-04-02 03:34:21.260 > but after sink by sql, data in kafka: > 2022-04-02 03:34:21.26 > {code} > > data miss end zero in kafka. > > sql: > {code:java} > create kafka_table(stime stimestamp) with ('connector'='kafka','format' = > 'json'); > insert into kafka_table select stime from (values(timestamp '2022-04-02 > 03:34:21.260')){code} > the value in kafka is : \{"stime":"2022-04-02 03:34:21.26"}, missed end zero. -- This message was sent by Atlassian Jira (v8.20.1#820001)