You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Dilip Biswal (JIRA)" <ji...@apache.org> on 2018/07/29 23:51:00 UTC

[jira] [Commented] (SPARK-24966) Fix the precedence rule for set operations.

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

Dilip Biswal commented on SPARK-24966:
--------------------------------------

I am working on a fix for this.

> Fix the precedence rule for set operations.
> -------------------------------------------
>
>                 Key: SPARK-24966
>                 URL: https://issues.apache.org/jira/browse/SPARK-24966
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.3.1
>            Reporter: Dilip Biswal
>            Priority: Major
>
> Currently the set operations INTERSECT, UNION and EXCEPT are assigned the same precedence. We need to change to make sure INTERSECT is given higher precedence than UNION and EXCEPT. UNION and EXCEPT should be evaluated in the order they appear in the query from left to right. 
> Given this will result in a change in behavior, we need to keep it under a config.
> Here is a reference :
> https://docs.microsoft.com/en-us/sql/t-sql/language-elements/set-operators-except-and-intersect-transact-sql?view=sql-server-2017



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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