[SPARK-51721][SQL] Change default value of ANALYZER_SINGLE_PASS_RESOLVER_RELATION_BRIDGING_ENABLED flag #50516
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
mihailoale-db
force-pushed
the
bridgingflagflip
branch
from
b08c25b to
79ad822
Compare
mihailoale-db
changed the title
mihailoale-db
force-pushed
the
bridgingflagflip
branch
from
79ad822 to
6953b14
Compare
mihailoale-db
force-pushed
the
bridgingflagflip
branch
from
6953b14 to
de75ac7
Compare
mihailoale-db
changed the title
vladimirg-db
approved these changes
Apr 8, 2025
|
@MaxGekk PTAL when you have time. Thanks! |
MaxGekk
approved these changes
Apr 8, 2025
MaxGekk
changed the title
|
+1, LGTM. Merging to master. |
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.
What changes were proposed in this pull request?
Change default value of
ANALYZER_SINGLE_PASS_RESOLVER_RELATION_BRIDGING_ENABLEDflag (set it totrue).Why are the changes needed?
To enable users to use dual run analysis bridging by default.
Does this PR introduce any user-facing change?
Users are going to use dual run analysis with bridging by default.
How was this patch tested?
Existing tests.
Was this patch authored or co-authored using generative AI tooling?
No.