[
https://issues.apache.org/jira/browse/FLINK-19795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jark Wu updated FLINK-19795:
----------------------------
Description: We are using Canal to synchornize MySQL data into Kafka, the
synchornization delivery is not exactly-once, so there might be dupcliate
INSERT/UPDATE/DELETE messages for the same primary key. We are using
{{'connecotr' = 'kafka', 'format' = 'canal-json'}} to consume such topic.
However, when appling TopN query on this created source table, the TopN
operator will thrown exception: {{Caused by: java.lang.RuntimeException: Can
not retract a non-existent record. This should never happen. }} (was: When
TOPN handles duplicate data, it will throw an exception :
"Can not retract a non-existent record. This should never happen.")
> When TOPN handles duplicate data, it will throw an exception
> -------------------------------------------------------------
>
> Key: FLINK-19795
> URL: https://issues.apache.org/jira/browse/FLINK-19795
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Runtime
> Affects Versions: 1.11.2
> Reporter: jinxin
> Priority: Major
>
> We are using Canal to synchornize MySQL data into Kafka, the synchornization
> delivery is not exactly-once, so there might be dupcliate
> INSERT/UPDATE/DELETE messages for the same primary key. We are using
> {{'connecotr' = 'kafka', 'format' = 'canal-json'}} to consume such topic.
> However, when appling TopN query on this created source table, the TopN
> operator will thrown exception: {{Caused by: java.lang.RuntimeException: Can
> not retract a non-existent record. This should never happen. }}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
