Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/16664
> Actually we are not only introducing new APIs, we are also breaking old
APIs in this patch. Please separate the bug fix part from the API changing part.
I actually disagree that this particular change should be a separate PR.
Part of exposing these new queries to the listener is providing information of
what these queries are doing, and the current (developer) API does not have a
way to expose that.
We can discuss ways of maybe exposing this information in a way that
doesn't break the existing API (I thought about a couple but I didn't like any
of them, so my preference was to just modify the existing developer) API. But I
strongly feel the bug fix is not complete without this information being
exposed in some way.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
