You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Cheng Lian (JIRA)" <ji...@apache.org> on 2016/06/02 05:23:59 UTC

[jira] [Updated] (SPARK-13484) Filter outer joined result using a non-nullable column from the right table

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

Cheng Lian updated SPARK-13484:
-------------------------------
    Assignee: Takeshi Yamamuro

> Filter outer joined result using a non-nullable column from the right table
> ---------------------------------------------------------------------------
>
>                 Key: SPARK-13484
>                 URL: https://issues.apache.org/jira/browse/SPARK-13484
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.5.2, 1.6.0, 2.0.0
>            Reporter: Xiangrui Meng
>            Assignee: Takeshi Yamamuro
>             Fix For: 2.0.0
>
>
> Technically speaking, this is not a bug. But
> {code}
> val a = sqlContext.range(10).select(col("id"), lit(0).as("count"))
> val b = sqlContext.range(10).select((col("id") % 3).as("id")).groupBy("id").count()
> a.join(b, a("id") === b("id"), "left_outer").filter(b("count").isNull).show()
> {code}
> returns nothing. This is because `b("count")` is not nullable and the filter condition is always false by static analysis. However, it is common for users to use `a(...)` and `b(...)` to filter the joined result.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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