[
https://issues.apache.org/jira/browse/SPARK-14986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268165#comment-15268165
]
Andrey Balmin edited comment on SPARK-14986 at 5/4/16 5:15 PM:
---------------------------------------------------------------
[~vsparmar] I don't know for sure - I don't work on Spark - I just use it. It
is clearly a Spark SQL issue, mostly likely, due to some incorrect rewrites in
the catalyst module.
was (Author: abalmin):
[~vsparmar] I don't know for sure - I don't work on Spark - I just use. It is
clearly a Spark SQL issue, mostly likely, due to some incorrect rewrites in the
catalyst module.
> Spark SQL returns incorrect results for LATERAL VIEW OUTER queries if all
> inner columns are projected out
> ---------------------------------------------------------------------------------------------------------
>
> Key: SPARK-14986
> URL: https://issues.apache.org/jira/browse/SPARK-14986
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 1.5.2
> Reporter: Andrey Balmin
>
> Repro: using Hive context, run this SQL query:
> select nil from (select 1 as x ) x LATERAL VIEW OUTER EXPLODE( array ())
> n as nil
> Actual result: returns 0 rows.
> Expected results: should return 1 row with null value.
> Details:
> If the query is modified to also return x:
> select x, nil from (select 1 as x ) x LATERAL VIEW OUTER EXPLODE( array
> ()) n as nil
> it works correctly and returns 1 row: [ 1, null ]
> Clearly, changing Select clause of a query should not change the number of
> rows it returns.
> Looking at the query plan it seems that the Generator object was
> (incorrectly) marked with “join=false"
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
