ThorneANN commented on PR #4302: URL: https://github.com/apache/flink-cdc/pull/4302#issuecomment-4029733475
> @ThorneANN Thank you for your comment. In the MySQL binlog protocol, apart from events like GTID events, there are mainly two types of events related to table names: DDL changes and row data changes (INSERT/UPDATE/DELETE). Currently, DDL changes are captured for all tables, partly because downstream DDL capture for online DDL tools may require DDL parsing for shadow tables. Aside from that, the main deserialization workload in the binlog client lies in parsing row data changes. Therefore, adding the table ID filtering logic specifically within the deserialization of these row change events is sufficient to achieve the optimization. Yes, the point that confuses me is that I noticed you added a lot of event serialization classes because I think you only need to filter tableids -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
