Hi Kevin, No, the state is not compatible but it is also not necessary because if the FlinkKafkaProducer is stopped with a savepoint all transactions are finalized and the new KafkaSink uses a different mechanism to track transaction ids. [1]
It should be enough to recover from the savepoint with the KafkaSink and ignore the FlinkKafkaProducer state. Best, Fabian [1] https://nightlies.apache.org/flink/flink-docs-release-1.14/release-notes/flink-1.14/#port-kafkasink-to-new-unified-sink-api-flip-143 On Tue, Jan 11, 2022 at 9:58 PM Kevin Lam <kevin....@shopify.com> wrote: > > Hi all, > > We're looking to migrating from FlinkKafkaProducer to the new KafkaSink for > the new unified Sink API. > > Is the state compatible across the two Kafka sink APIs? If not, what's the > best way to migrate from one to the other? > > Thanks in advance, > Kevin
