fix: use current shuffle config in aggregate test - #5439
Merged
sunchao merged 1 commit intoAug 23, 2026
Conversation
Member
Author
sunchao
approved these changes
Aug 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
Follow-up to #5055.
Rationale for this change
PR #5055 added an aggregate test using the removed
COMET_EXEC_SHUFFLE_ENABLEDconstant. Currentmaintherefore fails the Spark 3.4 Scalafix build while compiling test sources.What changes are included in this PR?
Use the current
COMET_SHUFFLE_ENABLEDconfig entry, matching the rest ofCometAggregateSuiteandCometConf.How are these changes tested?
The previously failing command now completes successfully: