Herman van Hövell created SPARK-49697:
-----------------------------------------
Summary: Figure out what to do with ExecutionListenerManager
Key: SPARK-49697
URL: https://issues.apache.org/jira/browse/SPARK-49697
Project: Spark
Issue Type: New Feature
Components: Connect, SQL
Affects Versions: 4.0.0
Reporter: Herman van Hövell
ExecutionListenerManager is a user facing API. It allows a user to track
queries executed by the current session. A user can register a listener that
implements QueryExecutionListener.
The problem here is that QueryExecutionListener uses QueryExecution.
QueryExecution is very much an internal class that exposes a lot of the gory
parts of spark sql. This not something we can expose in sql/api.
There are roughly two solutions here:
* Make this a classic only feature. We add a shim for QueryExecution, and
throw an exception when a Connect user tries to use this.
* Create a more lightweight version of query execution, and expose this for
both clients.
We'll probably end up doing the shims first, and doing the nice solution later.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
