[SPARK-28863][SQL][FOLLOWUP][3.0] Make sure optimized plan will not be re-analyzed #30872
Conversation
This file contains 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
…analyzed It's a known issue that re-analyzing an optimized plan can lead to various issues. We made several attempts to avoid it from happening, but the current solution `AlreadyOptimized` is still not 100% safe, as people can inject catalyst rules to call analyzer directly. This PR proposes a simpler and safer idea: we set the `analyzed` flag to true after optimization, and analyzer will skip processing plans whose `analyzed` flag is true. make the code simpler and safer no existing tests. Closes apache#30777 from cloud-fan/ds. Authored-by: Wenchen Fan <wenchen@databricks.com> Signed-off-by: HyukjinKwon <gurwls223@apache.org> (cherry picked from commit b4bea1a) Signed-off-by: HyukjinKwon <gurwls223@apache.org>
cloud-fan
changed the title
|
cc @HyukjinKwon |
|
Kubernetes integration test starting |
|
Kubernetes integration test status success |
|
Test build #133170 has finished for PR 30872 at commit
|
maropu
approved these changes
Dec 21, 2020
HyukjinKwon
approved these changes
Dec 22, 2020
|
Merged to branch-3.0. |
HyukjinKwon
pushed a commit
that referenced
this pull request
Dec 22, 2020
…e re-analyzed backport #30777 to 3.0 ---------- ### What changes were proposed in this pull request? It's a known issue that re-analyzing an optimized plan can lead to various issues. We made several attempts to avoid it from happening, but the current solution `AlreadyOptimized` is still not 100% safe, as people can inject catalyst rules to call analyzer directly. This PR proposes a simpler and safer idea: we set the `analyzed` flag to true after optimization, and analyzer will skip processing plans whose `analyzed` flag is true. ### Why are the changes needed? make the code simpler and safer ### Does this PR introduce _any_ user-facing change? no ### How was this patch tested? existing tests. Closes #30872 from cloud-fan/ds. Authored-by: Wenchen Fan <wenchen@databricks.com> Signed-off-by: HyukjinKwon <gurwls223@apache.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
backport #30777 to 3.0
What changes were proposed in this pull request?
It's a known issue that re-analyzing an optimized plan can lead to various issues. We made several attempts to avoid it from happening, but the current solution
AlreadyOptimizedis still not 100% safe, as people can inject catalyst rules to call analyzer directly.This PR proposes a simpler and safer idea: we set the
analyzedflag to true after optimization, and analyzer will skip processing plans whoseanalyzedflag is true.Why are the changes needed?
make the code simpler and safer
Does this PR introduce any user-facing change?
no
How was this patch tested?
existing tests.