Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/19981
> We are going to, right? Otherwise creating the interface just for SQL
doesn't align with your goal to centralize this part.
At some point, probably, but supporting streaming UIs in the SHS requires a
lot more work before we even reach that point. There are fundamental problems
with event logs and streaming apps that need to be resolved first.
> not catching event if users are not using SQL functions
Not sure why that would be an issue - or rather, why that's different from
the what's always been the case. Even if you have a SparkSession today you can
run non-SQL jobs using the underlying context, and those will generate events
that will be delivered to the SQL listener, and it has to deal with them (as it
does).
> I do think the previous code is cleaner than the current one.
What do you think about either of my suggestions to simplify the code?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
