[AURON #2457] Fix per-partition job submission in NativeCollectLimit - #2458
Open
lyne7-sc wants to merge 2 commits into
Open
[AURON #2457] Fix per-partition job submission in NativeCollectLimit#2458lyne7-sc wants to merge 2 commits into
lyne7-sc wants to merge 2 commits into
Conversation
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
1 participant
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?
Closes #2457
Rationale for this change
NativeCollectLimitBase.executeCollect()currently usestoLocalIterator, which submits a separate Spark job for every scanned partition.For empty or highly selective inputs, this can produce many unnecessary jobs and make driver-side scheduling dominate query execution.
What changes are included in this PR?
toLocalIteratorcollection loop withexecuteTake.Are there any user-facing changes?
Queries over empty or sparse partitions may submit fewer Spark jobs.
How was this patch tested?
Added a regression test to
AuronExecSuite.Was this patch authored or co-authored using generative AI tooling?
If yes, include:
Generated-by: GPT-5ASF guidance: https://www.apache.org/legal/generative-tooling.html