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

Sean Owen commented on SPARK-17298:
-----------------------------------

Agree, though spark.sql.crossJoin.enabled=false by default, so the queries 
result in an error right now. This disagrees with 
https://issues.apache.org/jira/browse/SPARK-17298?focusedCommentId=15446920&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15446920

This change allows it to work where it didn't before. I mean it's inaccurate to 
say that the change is to require this new syntax, because as before it can be 
allowed by changing the flag too.

> Require explicit CROSS join for cartesian products
> --------------------------------------------------
>
>                 Key: SPARK-17298
>                 URL: https://issues.apache.org/jira/browse/SPARK-17298
>             Project: Spark
>          Issue Type: Story
>          Components: SQL
>            Reporter: Srinath
>            Priority: Minor
>
> Require the use of CROSS join syntax in SQL (and a new crossJoin DataFrame 
> API) to specify explicit cartesian products between relations.
> By cartesian product we mean a join between relations R and S where there is 
> no join condition involving columns from both R and S.
> If a cartesian product is detected in the absence of an explicit CROSS join, 
> an error must be thrown. Turning on the spark.sql.crossJoin.enabled 
> configuration flag will disable this check and allow cartesian products 
> without an explicit cross join.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to