[
https://issues.apache.org/jira/browse/SPARK-18597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15700636#comment-15700636
]
Nattavut Sutyanyong commented on SPARK-18597:
---------------------------------------------
It's nice to learn through this JIRA that Spark supports {{left anti join}}
externally rather just being an internal form when rewriting {{NOT EXISTS}} or
{{NOT IN}}. If this is to follow the traditional join semantics, why does Spark
choose not to output the columns from the right table of a {{left anti join}}?
I guess the same question applies to {{left semi}} as well.
> Do not push down filters for LEFT ANTI JOIN
> -------------------------------------------
>
> Key: SPARK-18597
> URL: https://issues.apache.org/jira/browse/SPARK-18597
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Reporter: Herman van Hovell
> Priority: Minor
> Labels: correctness
>
> The optimizer pushes down filters for left anti joins. This unfortunately has
> the opposite effect. For example:
> {noformat}
> sql("create or replace temporary view tbl_a as values (1, 5), (2, 1), (3, 6)
> as t(c1, c2)")
> sql("create or replace temporary view tbl_b as values 1 as t(c1)")
> sql("""
> select *
> from tbl_a
> left anti join tbl_b on ((tbl_a.c1 = tbl_a.c2) is null or tbl_a.c1 =
> tbl_a.c2)
> """)
> {noformat}
> Should return rows [2, 1] & [3, 6], but returns no rows.
> The upside is that this will only happen when you use a really weird
> anti-join (only referencing the table on the left hand side).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
