LvYanquan created FLINK-36566:
---------------------------------

             Summary: Code optimization: always identify DataChangeEvent before 
SchemaChangeEvent in Operator
                 Key: FLINK-36566
                 URL: https://issues.apache.org/jira/browse/FLINK-36566
             Project: Flink
          Issue Type: Improvement
          Components: Flink CDC
    Affects Versions: cdc-3.3.0
            Reporter: LvYanquan
             Fix For: cdc-3.3.0


In a data flow system, the number of DataChangeEvents is always much larger 
than that of SchemaChangeEvents. If we always identify DataChangeEvents first 
(such as using an `instance of` judgment), it can reduce a lot of judgment 
logic and improve the performance.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to