[jira] [Created] (FLINK-23106) RetractableTopNFunction should send retract first and then send insert

["Jingsong Lee (Jira)" <ji...@apache.org>]

Jingsong Lee created FLINK-23106:
------------------------------------

             Summary: RetractableTopNFunction should send retract first and then send insert
                 Key: FLINK-23106
                 URL: https://issues.apache.org/jira/browse/FLINK-23106
             Project: Flink
          Issue Type: Bug
          Components: Table SQL / Runtime
            Reporter: Jingsong Lee
             Fix For: 1.14.0


Consider:

Source -> Rank(rownum=1) -> Join(key is partitionKey)

In this case, the downstream will produce the wrong result, even the wrong retraction (retract message that does not exist)
 * Rank output partition key + rownum , the rank here has row_ rownum=1
 * In the downstream join judgment rank output, rownum is 1, so assuming partition key is PK, do PK based optimization
 * Because select rownum, rank thinks that the PK of downstream data must be partition key + rownum, the retraction message of partition key is out of order, leading to problems in downstream PK based optimization

Fix: there is a problem with the rank implementation. It should not result in disordered retraction messages of partition key.

Bypass: do not select rownum of rank output



--
This message was sent by Atlassian Jira
(v8.3.4#803005)