[ https://issues.apache.org/jira/browse/FLINK-24608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timo Walther closed FLINK-24608. -------------------------------- Fix Version/s: 1.15.0 1.14.1 Release Note: This adds an additional operator to the topology if the new sink interfaces are used (e.g. for Kafka). It could cause issues in 1.14.1 when restoring from a 1.14 savepoint. A workaround is to cast the time attribute to a regular timestamp in the SQL statement closely before the sink. Resolution: Fixed Fixed in master: 548b96e9cb226aaf8d919d900c9326520a5b6dc8 Fixed in 1.14.1: 3719c0402ec979c619371fcde9f2e7d2c46d69ed For now I did not back port this fix to 1.13. 1.14 is still not adopted by many users whereas 1.13 is. The change could affect the savepoint restoration. > Sinks built with the unified sink framework do not receive timestamps when > used in Table API > -------------------------------------------------------------------------------------------- > > Key: FLINK-24608 > URL: https://issues.apache.org/jira/browse/FLINK-24608 > Project: Flink > Issue Type: Bug > Components: Connectors / Common, Table SQL / Planner > Affects Versions: 1.14.0, 1.13.3, 1.15.0 > Reporter: Fabian Paul > Assignee: Marios Trivyzas > Priority: Critical > Labels: pull-request-available > Fix For: 1.15.0, 1.14.1 > > > All sinks built with the unified sink framework extract the timestamp from > the internal {{StreamRecord}}. The Table API does not facilitate the > timestamp field in the {{StreamRecord}} but extracts the timestamp from the > actual data. > We either have to use a dedicated operator before all the sinks to simulate > the behavior or allow a customizable timestamp extraction during the sink > translation. -- This message was sent by Atlassian Jira (v8.20.1#820001)