[SPARK-27083][SQL]Add a new conf to control subqueryReuse #23998
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
10110346
changed the title
|
Test build #103116 has finished for PR 23998 at commit
|
Member
|
Could you please file a jira cuz this pr adds a new config? |
Contributor
Author
Ok,thanks |
10110346
changed the title
Contributor
|
thanks, merging to master! |
gatorsmile
added a commit
that referenced
this pull request
Jan 23, 2020
…k.sql.execution.subquery.reuse.enabled ### What changes were proposed in this pull request? This PR is to rename spark.sql.subquery.reuse to spark.sql.execution.subquery.reuse.enabled ### Why are the changes needed? Make it consistent and clear. ### Does this PR introduce any user-facing change? N/A. This is a [new conf added in Spark 3.0](#23998) ### How was this patch tested? N/A Closes #27346 from gatorsmile/spark27083. Authored-by: Xiao Li <[email protected]> Signed-off-by: Xiao Li <[email protected]>
j-baker
pushed a commit
to palantir/spark
that referenced
this pull request
Jan 25, 2020
## What changes were proposed in this pull request? Subquery Reuse and Exchange Reuse are not the same feature， if we don't want to reuse subqueries，and we just want to reuse exchanges，only one configuration that cannot be done. This PR adds a new configuration `spark.sql.subquery.reuse` to control subqueryReuse. ## How was this patch tested? N/A Closes apache#23998 from 10110346/SUBQUERY_REUSE. Authored-by: liuxian <[email protected]> Signed-off-by: Wenchen Fan <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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?
Subquery Reuse and Exchange Reuse are not the same feature， if we don't want to reuse subqueries，and we just want to reuse exchanges，only one configuration that cannot be done.
This PR adds a new configuration
spark.sql.subquery.reuseto control subqueryReuse.How was this patch tested?
N/A