Uh oh!
There was an error while loading. Please reload this page.
[SPARK-27088][SQL] Add a configuration to set log level for each batch at RuleExecutor - #24136
[SPARK-27088][SQL] Add a configuration to set log level for each batch at RuleExecutor#24136chakravarthiT wants to merge 2 commits into
Conversation
chakravarthiT
commented
Mar 18, 2019
@gengliangwang@HyukjinKwon Please review. |
HyukjinKwon
commented
Mar 19, 2019
cc @maryannxue |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
maryannxue
left a comment
There was a problem hiding this comment.
LGTM, except some minor suggestions.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
gatorsmile
commented
Mar 21, 2019
ok to test |
SparkQA
commented
Mar 21, 2019
Test build #103756 has finished for PR 24136 at commit
|
maropu
commented
Mar 21, 2019
retest this please |
Uh oh!
There was an error while loading. Please reload this page.
SparkQA
commented
Mar 21, 2019
Test build #103760 has finished for PR 24136 at commit
|
chakravarthiT
commented
Mar 21, 2019
looks like non-relevant failure. |
maropu
commented
Mar 22, 2019
retest this please |
SparkQA
commented
Mar 22, 2019
Test build #103799 has finished for PR 24136 at commit
|
SparkQA
commented
Mar 22, 2019
Test build #103801 has finished for PR 24136 at commit
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
…l" to batch plan change in RuleExecutor
SparkQA
commented
Mar 26, 2019
Test build #103991 has finished for PR 24136 at commit
|
@maropu@HyukjinKwon handled review comments. and now that UT is passed,as message will be evaluated only when specific log level is set. |
| } else { | ||
| logTrace(s"Batch ${batch.name} has no effect.") | ||
| } | ||
| planChangeLogger.logBatch(batch.name, batchStartPlan, curPlan) |
There was a problem hiding this comment.
The config "spark.sql.optimizer.planChangeLog.level", is used for logging plan changes after applying rule or batch . As per Line 148,it is logging when there is no change in plan,which conflicts the parameter(spark.sql.optimizer.planChangeLog.level). Its not required to log this.
There was a problem hiding this comment.
Please address them in a followup if there are further comments.
gatorsmile
commented
Mar 27, 2019
LGTM except the above comment. |
HyukjinKwon
commented
Apr 10, 2019
retest this please |
SparkQA
commented
Apr 10, 2019
Test build #104485 has finished for PR 24136 at commit
|
HyukjinKwon
commented
Apr 11, 2019
Merged to master. |
What changes were proposed in this pull request?
Similar to #22406 , which has made log level for plan changes by each rule configurable ,this PR is to make log level for plan changes by each batch configurable,and I have reused the same configuration: "spark.sql.optimizer.planChangeLog.level".
Config proposed in this PR ,
spark.sql.optimizer.planChangeLog.batches - enable plan change logging only for a set of specified batches, separated by commas.
How was this patch tested?
Added UT , also tested manually and attached screenshots below.
1)Setting spark.sql.optimizer.planChangeLog.leve to warn.
2)setting spark.sql.optimizer.planChangeLog.batches to Resolution and Subquery.
