[GitHub] [spark] chakravarthiT opened a new pull request #24136: [SPARK-27088][SQL] Apply conf "spark.sql.optimizer.planChangeLog.leve…

Mon, 18 Mar 2019 12:15:58 -0700 

chakravarthiT opened a new pull request #24136: [SPARK-27088][SQL] Apply conf 
"spark.sql.optimizer.planChangeLog.leve…
URL: https://github.com/apache/spark/pull/24136
 
 
   ## 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.
   
   
![settingLogLevelToWarn](https://user-images.githubusercontent.com/45845595/54556730-8803dd00-49df-11e9-95ab-ebb0c8d735ef.png)
   
   2)setting spark.sql.optimizer.planChangeLog.batches to Resolution and 
Subquery.
   
![settingBatchestoLog](https://user-images.githubusercontent.com/45845595/54556740-8cc89100-49df-11e9-80ab-fbbbe1ff2cdf.png)
   
   3)  plan change logging enabled only for a set of specified 
batches(Resolution and Subquery)
   
![batchloggingOp](https://user-images.githubusercontent.com/45845595/54556788-ab2e8c80-49df-11e9-9ae0-57815f552896.png)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to