You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Carson Wang (JIRA)" <ji...@apache.org> on 2015/10/20 11:17:27 UTC

[jira] [Commented] (SPARK-11206) Support SQL UI on the history server

    [ https://issues.apache.org/jira/browse/SPARK-11206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964841#comment-14964841 ] 

Carson Wang commented on SPARK-11206:
-------------------------------------

I am working on this. I plan to add an onOtherEvent method to the SparkListener trait and post all SQL related events to the same event bus. That is, we'll write SparkListenerSQLExecutionStart and SparkListenerSQLExecutionEnd events to the event log.
One problem I encounter is that the core module can't import class from the sql module. So I need define these SQL events and related SQL data structures (like spark plan info) in the core module. It seems I also need move SQLTab, SQLListener, etc to the core module so that I can attach the SQL tab to the Spark history UI. Any suggestion is appreciated. [~zsxwing] 

> Support SQL UI on the history server
> ------------------------------------
>
>                 Key: SPARK-11206
>                 URL: https://issues.apache.org/jira/browse/SPARK-11206
>             Project: Spark
>          Issue Type: New Feature
>          Components: SQL, Web UI
>            Reporter: Carson Wang
>
> On the live web UI, there is a SQL tab which provides valuable information for the SQL query. But once the workload is finished, we won't see the SQL tab on the history server. It will be helpful if we support SQL UI on the history server so we can analyze it even after its execution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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