[jira] [Resolved] (SPARK-53244) Don't store dual-run enabled and tentative mode enabled confs during view creation

["Wenchen Fan (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-53244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wenchen Fan resolved SPARK-53244.
---------------------------------
    Resolution: Fixed

Issue resolved by pull request 51972
[https://github.com/apache/spark/pull/51972]

> Don't store dual-run enabled and tentative mode enabled confs during view creation
> ----------------------------------------------------------------------------------
>
>                 Key: SPARK-53244
>                 URL: https://issues.apache.org/jira/browse/SPARK-53244
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 4.0.0
>            Reporter: Mihailo Aleksic
>            Assignee: Mihailo Aleksic
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.1.0
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org