[
https://issues.apache.org/jira/browse/SPARK-11206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14973700#comment-14973700
]
Carson Wang commented on SPARK-11206:
-------------------------------------
For the live SQL UI, the SQLContext is responsible for attaching the SQLTab and
adding the SQLListener.
The history server, the standalone Master that rebuilds web UI, and the event
log listener which writes events to the storage are all in the core module.
Since there is no SQLContext for history UI, these components in the core need
reference the SQL class like SQLTab, SQLListener and the SQL events.
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
