[
https://issues.apache.org/jira/browse/SPARK-32555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17172056#comment-17172056
]
Apache Spark commented on SPARK-32555:
--------------------------------------
User 'HeartSaVioR' has created a pull request for this issue:
https://github.com/apache/spark/pull/29372
> Add unique ID on QueryExecution to enable listeners to deduplicate
> -------------------------------------------------------------------
>
> Key: SPARK-32555
> URL: https://issues.apache.org/jira/browse/SPARK-32555
> Project: Spark
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 3.1.0
> Reporter: Jungtaek Lim
> Priority: Minor
>
> Somehow there's a change 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.
> This issue tracks the effort on adding unique ID on QueryExecution, so that
> listener can leverage the ID to deduplicate callbacks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
