spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wenchen Fan (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-21335) support un-aliased subquery
Date Fri, 07 Jul 2017 12:06:01 GMT

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

Wenchen Fan resolved SPARK-21335.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.3.0

Issue resolved by pull request 18559
[https://github.com/apache/spark/pull/18559]

> support un-aliased subquery
> ---------------------------
>
>                 Key: SPARK-21335
>                 URL: https://issues.apache.org/jira/browse/SPARK-21335
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.3.0
>            Reporter: Wenchen Fan
>            Assignee: Wenchen Fan
>              Labels: release-notes
>             Fix For: 2.3.0
>
>
> un-aliased subquery is supported by Spark SQL for a long time. Its semantic was not well
defined and has confusing behaviors, and it's not a standard SQL syntax, so we disallowed
it in https://issues.apache.org/jira/browse/SPARK-20690 .
> However, this is a breaking change, and we do have existing queries using un-aliased
subquery. We should add the support back and fix its semantic.
> After the fix, there is no syntax change from branch 2.2 to master, but we invalid a
weird use case:
> {{SELECT v.i from (SELECT i FROM v)}}. Now this query will throw analysis exception because
users should not be able to use the qualifier inside a subquery.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message