You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2020/08/08 22:10:00 UTC

[jira] [Resolved] (SPARK-32555) Add unique ID on QueryExecution to enable listeners to deduplicate

     [ https://issues.apache.org/jira/browse/SPARK-32555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dongjoon Hyun resolved SPARK-32555.
-----------------------------------
    Fix Version/s: 3.1.0
       Resolution: Fixed

Issue resolved by pull request 29372
[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
>            Assignee: Jungtaek Lim
>            Priority: Minor
>             Fix For: 3.1.0
>
>
> 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-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org