You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (JIRA)" <ji...@apache.org> on 2019/02/16 09:07:00 UTC

[jira] [Resolved] (SPARK-26864) Query may return incorrect result when python udf is used as a join condition and the udf uses attributes from both legs of left semi join.

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

Wenchen Fan resolved SPARK-26864.
---------------------------------
       Resolution: Fixed
         Assignee: Dilip Biswal
    Fix Version/s: 3.0.0
                   2.4.1

> Query may return incorrect result when python udf is used as a join condition and the udf uses attributes from both legs of left semi join.
> -------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-26864
>                 URL: https://issues.apache.org/jira/browse/SPARK-26864
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.4.0
>            Reporter: Dilip Biswal
>            Assignee: Dilip Biswal
>            Priority: Major
>             Fix For: 2.4.1, 3.0.0
>
>
> In SPARK-25314, we supported the scenario of having a python UDF that refers to attributes from both legs of a join condition by rewriting
> the plan to convert an inner join or left semi join to a filter over a cross join. In case of left semi join, this transformation may
> cause incorrect results when the right leg of join condition produces duplicate rows based on the join condition.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org