[SPARK-51559][SQL] Make max broadcast table size configurable#54566
Closed
pratham76 wants to merge 1 commit intoapache:branch-4.0from
Closed
[SPARK-51559][SQL] Make max broadcast table size configurable#54566pratham76 wants to merge 1 commit intoapache:branch-4.0from
pratham76 wants to merge 1 commit intoapache:branch-4.0from
Conversation
Contributor
Author
|
@dongjoon-hyun @viirya @cloud-fan @sunchao Could you provide your thoughts on this backport? |
Contributor
Author
|
@dongjoon-hyun @pan3793 Gentle ping! |
Member
|
@pratham76 it's an improvement/feature, not a bug, we generally don't backport for this case. for more details, please read "Policy on backporting bug fixes" section in https://spark.apache.org/committers.html |
Contributor
Author
|
Thanks for the info, closing this PR |
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.
What changes were proposed in this pull request?
This PR is a backport of #50327 to spark 4.0.x versions, as it is good to have.
Why are the changes needed?
This PR introduces a new configuration: spark.sql.maxBroadcastTableSize, This would allow users to broadcast larger tables (>8GB) when necessary to be more flexible.
Does this PR introduce any user-facing change?
How was this patch tested?
Existing UTs
Was this patch authored or co-authored using generative AI tooling?
No