[jira] [Resolved] (SPARK-33042) Add a test case to ensure changes to spark.sql.optimizer.maxIterations take effect at runtime

["Hyukjin Kwon (Jira)" <ji...@apache.org>]

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

Hyukjin Kwon resolved SPARK-33042.
----------------------------------
    Fix Version/s: 3.1.0
       Resolution: Fixed

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

> Add a test case to ensure changes to spark.sql.optimizer.maxIterations take effect at runtime
> ---------------------------------------------------------------------------------------------
>
>                 Key: SPARK-33042
>                 URL: https://issues.apache.org/jira/browse/SPARK-33042
>             Project: Spark
>          Issue Type: Test
>          Components: SQL
>    Affects Versions: 3.1.0
>            Reporter: Yuning Zhang
>            Assignee: Yuning Zhang
>            Priority: Major
>             Fix For: 3.1.0
>
>
> **Add a test case to ensure changes to `spark.sql.optimizer.maxIterations` take effect at runtime.
> Currently, there is only one related test case: [https://github.com/apache/spark/blob/master/sql/core/src/test/scala/org/apache/spark/sql/internal/SQLConfSuite.scala#L156]
> However, this test case only checks the value of the conf can be changed at runtime. It does not check the updated value is actually used by the Optimizer.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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