HeartSaVioR opened a new pull request #29372: URL: https://github.com/apache/spark/pull/29372
### What changes were proposed in this pull request? This PR adds unique ID on QueryExecution, so that listeners can leverage the ID to deduplicate redundant calls. ### Why are the changes needed? I've observed that Spark calls QueryExecutionListener multiple times on same QueryExecution instance (even same funcName for onSuccess). There's no unique ID on QueryExecution, hence it's a bit tricky if the listener would like to deal with same query execution only once. Note that streaming query has both query ID and run ID which can be leveraged as unique ID. ### Does this PR introduce _any_ user-facing change? Yes for who uses query execution listener - they'll see `id` field in QueryExecution and leverage it. ### How was this patch tested? Manually tested. I think the change is obvious hence don't think it warrants a new UT. StreamingQueryListener has been using UUID as `queryId` and `runId` so it should work for the same. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
