haruki-830 opened a new pull request, #4526: URL: https://github.com/apache/flink-cdc/pull/4526
## What is the purpose of this pull request? JIRA: https://issues.apache.org/jira/browse/FLINK-40552 This PR introduces opt-in ordered asynchronous execution for post-transform processing. It improves the throughput of I/O-bound transform expressions, such as AI model calls, while preserving CDC event ordering and schema consistency. ## Brief change log - Extract the common post-transform logic into `PostTransformProcessor` for both synchronous and asynchronous execution. - Add asynchronous execution options for enablement, timeout, capacity, and worker threads. - Use ordered asynchronous waiting so that `DataChangeEvent`s can execute concurrently while outputs remain ordered. - Treat `SchemaChangeEvent`s as barriers to preserve schema/data ordering. - Preserve schema state across checkpoints and same-parallelism savepoints. - Emit the restored `CreateTableEvent` only once before subsequent data events. - Add compatibility adapters for both Flink 1.x and Flink 2.x. - Document asynchronous execution options and thread-safety requirements. ## Verifying this change This change added unit tests covering: - Concurrent execution and ordered output of data change events. - Schema change barriers and schema/data ordering. - Timeout and transform exception propagation. - Checkpoint restoration. - Same-parallelism savepoint restoration. - Exactly-once emission of the restored `CreateTableEvent`. - Selection of the asynchronous post-transform operator by the composer. ## Documentation - Does this pull request introduce a new feature? yes - If yes, how is the feature documented? docs and JavaDocs --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — OpenAI Codex (GPT-5) Generated-by: OpenAI Codex (GPT-5) -- 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]
