spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dylan Guedes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-28553) subqueries must be aggregated before hand
Date Tue, 30 Jul 2019 12:07:00 GMT

    [ https://issues.apache.org/jira/browse/SPARK-28553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896064#comment-16896064
] 

Dylan Guedes commented on SPARK-28553:
--------------------------------------

Oh, my bad. I even look'd for an already created JIRA, idk why I didn't find the one that
you created (maybe I used the wrong terms). I'll edit my PR to use your JIRA Instead and I'll
close this one. Thank you [~yumwang]

> subqueries must be aggregated before hand
> -----------------------------------------
>
>                 Key: SPARK-28553
>                 URL: https://issues.apache.org/jira/browse/SPARK-28553
>             Project: Spark
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 3.0.0
>            Reporter: Dylan Guedes
>            Priority: Major
>
> Looks like Spark subqueries does not work well with variables and values from outside
of subquery. For instance, this query work on PgSQL:
>  {code:sql}
> SELECT lead(ten, (SELECT two FROM tenk1 WHERE s.unique2 = unique2)) OVER (PARTITION BY
four ORDER BY ten) FROM tenk1 s WHERE unique2 < 10;{code}
> However, it does not work in Spark.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

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


Mime
View raw message