[
https://issues.apache.org/jira/browse/FLINK-23850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17407198#comment-17407198
]
Timo Walther edited comment on FLINK-23850 at 8/31/21, 9:25 AM:
----------------------------------------------------------------
[~mapohl] you could implement the same pipeline as in
https://github.com/apache/flink/pull/17060/files#diff-a08bcfb72b9ea9207dbc53c4149608589136f22c1f8b6acb1a84083708d18807
with Kafka upsert, it discovered already a couple of issues. Please note that
the Kafka connector was broken for some SQL queries before FLINK-23895.
was (Author: twalthr):
[~mapohl] you could implement the same pipeline as in
https://github.com/apache/flink/pull/17060/files#diff-a08bcfb72b9ea9207dbc53c4149608589136f22c1f8b6acb1a84083708d18807
with Kafka upsert, it discovered already a couple of issues.
> Test Kafka table connector with new runtime provider
> ----------------------------------------------------
>
> Key: FLINK-23850
> URL: https://issues.apache.org/jira/browse/FLINK-23850
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Kafka
> Affects Versions: 1.14.0
> Reporter: Qingsheng Ren
> Assignee: Matthias
> Priority: Blocker
> Labels: release-testing
> Fix For: 1.14.0
>
>
> The runtime provider of Kafka table connector has been replaced with new
> KafkaSource and KafkaSink. The table connector requires to be tested to make
> sure nothing is surprised to Table/SQL API users.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
