Wenchen Fan d3a1d9527b [SPARK-22786][SQL] only use AppStatusPlugin in history server ... ## What changes were proposed in this pull request? In https://github.com/apache/spark/pull/19681 we introduced a new interface called `AppStatusPlugin`, to register listeners and set up the UI for both live and history UI. However I think it's an overkill for live UI. For example, we should not register `SQLListener` if users are not using SQL functions. Previously we register the `SQLListener` and set up SQL tab when `SparkSession` is firstly created, which indicates users are going to use SQL functions. But in #19681 , we register the SQL functions during `SparkContext` creation. The same thing should apply to streaming too. I think we should keep the previous behavior, and only use this new interface for history server. To reflect this change, I also rename the new interface to `SparkHistoryUIPlugin` This PR also refines the tests for sql listener. ## How was this patch tested? existing tests Author: Wenchen Fan <wenchen@databricks.com> Closes #19981 from cloud-fan/listener.		2017-12-22 01:08:13 +08:00
..
src	[SPARK-22786][SQL] only use AppStatusPlugin in history server	2017-12-22 01:08:13 +08:00
pom.xml	[SPARK-19112][CORE] Support for ZStandard codec	2017-11-01 14:54:08 +01:00