-
Notifications
You must be signed in to change notification settings - Fork 29k
[SPARK-11068][SQL] add callback to query execution #9078
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
cc @yhuai |
|
Test build #43579 has finished for PR 9078 at commit
|
|
Test build #43583 has finished for PR 9078 at commit
|
|
Does this need to be a public interface? If yes, can we add experimental label to it. |
|
Actually if QueryExecution is not a public interface (it is in execution - I think it's incorrectly labeled developer api), this should probably be in execution as well as a semi private interface? |
|
Test build #43592 has finished for PR 9078 at commit
|
|
retest this please. |
|
Test build #43600 has finished for PR 9078 at commit
|
|
Test build #43604 has finished for PR 9078 at commit
|
|
Test build #43626 has finished for PR 9078 at commit
|
|
retest this please. |
|
Test build #43637 has finished for PR 9078 at commit
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be thread-safe.
|
retest this please. |
|
Test build #43652 has finished for PR 9078 at commit
|
|
Test build #43660 has finished for PR 9078 at commit
|
|
Test build #43667 has finished for PR 9078 at commit
|
|
Test build #43674 has finished for PR 9078 at commit
|
|
LGTM, waiting for tests. |
|
Test build #43685 has finished for PR 9078 at commit
|
|
Merged into master, thanks! |
…on thread ## What changes were proposed in this pull request? The SQL execution listener framework was created from scratch(see apache#9078). It didn't leverage what we already have in the spark listener framework, and one major problem is, the listener runs on the spark execution thread, which means a bad listener can block spark's query processing. This PR re-implements the SQL execution listener framework. Now `ExecutionListenerManager` is just a normal spark listener, which watches the `SparkListenerSQLExecutionEnd` events and post events to the user-provided SQL execution listeners. ## How was this patch tested? existing tests. Closes apache#22674 from cloud-fan/listener. Authored-by: Wenchen Fan <[email protected]> Signed-off-by: Wenchen Fan <[email protected]>
With this feature, we can track the query plan, time cost, exception during query execution for spark users.