You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Takeshi Yamamuro (Jira)" <ji...@apache.org> on 2019/12/09 10:45:00 UTC
[jira] [Resolved] (SPARK-30138) Separate configuration key of max
iterations for analyzer and optimizer
[ https://issues.apache.org/jira/browse/SPARK-30138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Takeshi Yamamuro resolved SPARK-30138.
--------------------------------------
Fix Version/s: 3.0.0
Assignee: Hu Fuwang
Resolution: Fixed
Resolved by https://github.com/apache/spark/pull/26766
> Separate configuration key of max iterations for analyzer and optimizer
> -----------------------------------------------------------------------
>
> Key: SPARK-30138
> URL: https://issues.apache.org/jira/browse/SPARK-30138
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.0.0
> Reporter: Hu Fuwang
> Assignee: Hu Fuwang
> Priority: Major
> Fix For: 3.0.0
>
>
> Currently, both Analyzer and Optimizer use conf "spark.sql.optimizer.excludedRules" to set the max iterations to run, which is a little confusing.
> It is clearer to add a new conf "spark.sql.analyzer.excludedRules" for analyzer max iterations.
--
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