xuanyuanking opened a new pull request #23371: [SPARK-26223][SQL] Track 
metastore operation time in scan node
URL: https://github.com/apache/spark/pull/23371
 
 
   ## What changes were proposed in this pull request?
   
   As the comment in 
[SPARK-26223](https://issues.apache.org/jira/browse/SPARK-26223?focusedCommentId=16723111&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16723111),
 track all metastore operation time in scan node and show the duration in 
metrics as well as the timeline when hover. The mainly changes including:
   - Add `metastoreOpsPhaseSummaries` in CatalogTable param list for recording 
all timeline between the table and the metastore.
   - Create phase summaries in all scenarios described in Jira and memorize 
them into `metastoreOpsPhaseSummaries`.
   - Display support and driver metrics updating for metastore operations.
   
   ## How was this patch tested?
   Add UT in SQLMetricsSuite.
   Manually test and check UI:
   
   |             Scenario            | UI |
   |:-------------------------------:|----|
   | FileSourceScanExec with partition pruning 
|![image](https://user-images.githubusercontent.com/4833765/50370288-04547300-05df-11e9-9bab-549c89d180fa.png)|
   | HiveTableScanExec 
|![image](https://user-images.githubusercontent.com/4833765/50370268-ae7fcb00-05de-11e9-9f4c-eeb8e3e8f2d1.png)|
   | FileSourceScanExec with RelationConversion for hive table 
|![image](https://user-images.githubusercontent.com/4833765/50370310-5e553880-05df-11e9-98af-766248504fc8.png)|
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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