yunfengzhou-hub opened a new pull request, #5877: URL: https://github.com/apache/paimon/pull/5877
### Purpose Linked issue: close #5876 This PR fixes the problems that affect the stability of Flink 2.0 test workflow and add back the workflow script again, which was once removed in https://github.com/apache/paimon/commit/a6d2e8376cfb93accfbb2112048edefeb48bc77e. I counted the most recent 100 Action executions before the script is removed, and the problems that caused the failures are as follows. 1. (79%) The Action run successfully. 2. (11%) paimon-e2e-tests relies on paimon-flink-cdc, which is not compiled with -Pflink2. The Action failed with a timeout exception when trying to download the latest snapshot of this module. 3. (7%) CatalogTableITCase#testConsumersTable failed. It is a flaky test with race condition. 4. (3%) Various failures that appeared only once. So we need to fix the problems mentioned in 2 and 3 before enabling the Action again. #### Build paimon-flink-cdc under Flink 2.0 Example failure Action log: https://github.com/apache/paimon/actions/runs/15804130573/job/44546474506 The failure was because that `paimon-e2e-tests` and `paimon-docs` relies on `paimon-flink-cdc` module, but this module is not compiled when profile `flink2` is enabled. In the attempt to download the snapshot of this module, network connection timeout might occur. This PR fixes the failure by enabling the compilation of `paimon-flink-cdc` and its pre-module (`paimon-flink1-common`) under `-Pflink2`. This change is supposed not to affect the production code and the releasing process. #### Fix race condition in CatalogTableITCase#testConsumersTable Example failure Action log: https://github.com/apache/paimon/actions/runs/15822438299/job/44594579766 This failure was because that the Flink job with the consumer source might not have completed its initialization before the second batch of data is written to the Paimon table. In order to fix it, a blocking operation is added to force the test case to wait for the source's initialization before the next write. ### Tests <!-- List UT and IT cases to verify this change --> ### API and Format <!-- Does this change affect API or storage format --> ### Documentation <!-- Does this change introduce a new feature --> -- 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]
