You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[SPARK-53244][SQL] Don't store dual-run enabled and tentative mode enabled confs during view creation
### What changes were proposed in this pull request?
If a `ANALYZER_DUAL_RUN_LEGACY_AND_SINGLE_PASS_RESOLVER` conf is explicitly set during view creation, we store it, but we might not want to. When we query that view, stored value is used, which we forbid in order to avoid any accidental failures. We do the same for `ANALYZER_SINGLE_PASS_RESOLVER_ENABLED_TENTATIVELY`.
### Why are the changes needed?
To make single-pass resolver runs more stable.
### Does this PR introduce _any_ user-facing change?
N/A
### How was this patch tested?
Added tests.
### Was this patch authored or co-authored using generative AI tooling?
No.
Closes#51972 from mihailoale-db/dontstoreqanconfs.
Authored-by: mihailoale-db <[email protected]>
Signed-off-by: Wenchen Fan <[email protected]>
0 commit comments