[FLINK-36566] Code optimization: always identify DataChangeEvent before SchemaChangeEvent in Operator

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: cdc-3.3.0
• Fix Version/s: cdc-3.3.0
• Component/s: Flink CDC
• Assignee: Unassigned
• Reporter: Yanquan Lv
• Created: 18/Oct/24 04:08
• Updated: 18/Oct/24 04:08

Description

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.