You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (JIRA)" <ji...@apache.org> on 2019/04/11 01:04:00 UTC

[jira] [Resolved] (SPARK-27088) Apply conf "spark.sql.optimizer.planChangeLog.level" to batch plan change in RuleExecutor

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

Hyukjin Kwon resolved SPARK-27088.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0

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

> Apply conf "spark.sql.optimizer.planChangeLog.level" to batch plan change in RuleExecutor
> -----------------------------------------------------------------------------------------
>
>                 Key: SPARK-27088
>                 URL: https://issues.apache.org/jira/browse/SPARK-27088
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Maryann Xue
>            Assignee: Chakravarthi
>            Priority: Minor
>             Fix For: 3.0.0
>
>
> Similar to SPARK-25415, which has made log level for plan changes by each rule configurable, we can make log level for plan changes by each batch configurable too and can reuse the same configuration: "spark.sql.optimizer.planChangeLog.level".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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