Github user carsonwang commented on the pull request:
https://github.com/apache/spark/pull/10061#issuecomment-160889037
Hi @JoshRosen, the execution IDs are from the static `SQLExecution` object.
So I think they are always unique. Yes, previously each `SQLContext` has its
own `SQLListener`. Since the SQL events are now sent to the same event bus, all
`SQLListeners` will receives SQL events executed from other `SQLContexts`. If
we still want to keep one UI Tab for each `SQLContext`, I think we need keep
something like a SQLContext ID in the SQL event so that the `SQLListener` knows
if it need handle that event. Is there any strong requirement to keep one UI
Tab for each `SQLContext`? I remember some users don't want so many UI tabs
because they create many `SQLContext`.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
