GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/1123
[SPARK-2187] Explain should not run the optimizer twice.
@yhuai @marmbrus
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark explain
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1123#issuecomment-46514203
Nice, this LGTM. This will also make it easy to possibly add the option to
view the optimized logical plan though explain at some point as well.
---
If your project
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1123#discussion_r13949859
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/commands.scala ---
@@ -71,16 +72,24 @@ case class SetCommand(
}
/**
+ *
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1123#discussion_r13949881
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/commands.scala ---
@@ -71,16 +72,24 @@ case class SetCommand(
}
/**
+ * An
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1123#issuecomment-46514306
Merged build started.
---
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 project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1123#issuecomment-46517788
Merged build finished.
---
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 project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1123#issuecomment-46517789
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15886/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1123#issuecomment-46522444
Merged build triggered.
---
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 project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1123#issuecomment-46522447
Merged build started.
---
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 project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1123#issuecomment-46525501
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1123#issuecomment-46525503
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15893/
---
If your
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1123#issuecomment-46525610
Ok I am merging this in master branch-1.0.
---
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 project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1123
---
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 project does not have this feature
enabled and wishes so, or if the feature is
13 matches
Mail list logo
