Github user sameeragarwal commented on a diff in the pull request:
https://github.com/apache/spark/pull/13209#discussion_r64112716
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -348,6 +348,11 @@ object SQLConf {
.booleanConf
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13209#discussion_r63990349
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -348,6 +348,11 @@ object SQLConf {
.booleanConf
Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/13209#discussion_r63987980
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/internal/SQLConf.scala ---
@@ -348,6 +348,11 @@ object SQLConf {
.booleanConf
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13209#issuecomment-220505869
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13209#issuecomment-220505867
Merged build finished. Test FAILed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13209#issuecomment-220505801
**[Test build #58933 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58933/consoleFull)**
for PR 13209 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/13209#issuecomment-220504465
Yeah, thats a good idea. They might not even know which join is getting
planned that way otherwise.
---
If your project is set up for it, you can reply to this
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/13209#discussion_r63984891
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -178,7 +178,12 @@ private[sql] abstract class SparkStrategies
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13209#issuecomment-220503450
cc @marmbrus
I'm wondering if it'd be better to do this check before execution, rather
than in planning. The reason is that we would then be able to run explain on
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13209#discussion_r63984279
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -178,7 +178,12 @@ private[sql] abstract class SparkStrategies
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/13209#discussion_r63984257
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -178,7 +178,12 @@ private[sql] abstract class SparkStrategies
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13209#issuecomment-220500702
**[Test build #58933 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58933/consoleFull)**
for PR 13209 at commit
GitHub user sameeragarwal opened a pull request:
https://github.com/apache/spark/pull/13209
[SPARK-15425][SQL] Disallow cartesian joins by default
## What changes were proposed in this pull request?
In order to prevent users from inadvertently writing queries with cartesian
13 matches
Mail list logo
