Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[SPARK-48260][SQL] Disable output committer coordination in one test …
…of ParquetIOSuite ### What changes were proposed in this pull request? A test from `ParquetIOSuite` is flaky: `SPARK-7837 Do not close output writer twice when commitTask() fails` It turns out to be a race condition. The test injects error to the task committing step, and the job may fail in two ways: 1. The task got the driver's permission to commit the task, but the committing failed and thus the task failed. This will trigger a stage failure as it means possible data duplication, see #36564 2. In test we disable task retry, so `TaskSetManager` will abort the stage. Both these two failures are done by sending an event to `DAGScheduler`, so the final job failure depends on which event gets processed first. This is not a big deal, but that test in `ParquetIOSuite` checks the error class. This PR fixes the flaky test by running the test case in a new test suite with output committer coordination disabled ### Why are the changes needed? fix flaky test ### Does this PR introduce _any_ user-facing change? no ### How was this patch tested? GA test + manual test on lcoal ### Was this patch authored or co-authored using generative AI tooling? No Closes #46562 from gengliangwang/fixParquetIO. Authored-by: Gengliang Wang <[email protected]> Signed-off-by: Gengliang Wang <[email protected]>
- Loading branch information