Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/9762#discussion_r45300217
--- Diff: sql/core/src/test/scala/org/apache/spark/sql/SQLQuerySuite.scala
---
@@ -1997,4 +1997,18 @@ class SQLQuerySuite extends QueryTest with
Github user aray commented on a diff in the pull request:
https://github.com/apache/spark/pull/9815#discussion_r45300236
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/Analyzer.scala
---
@@ -211,45 +211,31 @@ class Analyzer(
GitHub user gatorsmile opened a pull request:
https://github.com/apache/spark/pull/9832
[SPARK-11848][SQL] Support EXPLAIN in DataSet APIs
When debugging DataSet API, I always need to print the logical and physical
plans.
I am wondering if we should provide a simple API
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-157952122
Merged build finished. Test PASSed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-157952123
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157953219
**[Test build #46299 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46299/consoleFull)**
for PR 9785 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9832#issuecomment-157955129
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/9602#issuecomment-157876030
**[Test build #2089 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2089/consoleFull)**
for PR 9602 at commit
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/9821
[SPARK-11830][Core]Make NettyRpcEnv bind to the specified host
This PR includes the following change:
1. Bind NettyRpcEnv to the specified host
2. Fix the port information in the log
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/9739#issuecomment-157877564
Can you add a test?
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9797#issuecomment-157877686
**[Test build #46234 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46234/consoleFull)**
for PR 9797 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9530#issuecomment-157885830
**[Test build #46261 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46261/consoleFull)**
for PR 9530 at commit
Github user hvanhovell commented on a diff in the pull request:
https://github.com/apache/spark/pull/9819#discussion_r45271240
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -25,7 +25,7 @@ import scala.collection.mutable.ArrayBuffer
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/9799#issuecomment-157892279
+1 to @JoshRosen's suggestion, which is actually @davies' original
proposal. Even though we don't use broadcast `BytesToBytesMap` currently I
think it's still a good
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9820#issuecomment-157905355
**[Test build #46248 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46248/consoleFull)**
for PR 9820 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/9773#issuecomment-157905396
If we can get a test case soon we can still include this in Spark 1.6.
Also please make the title: `[SPARK-11778] [SQL] Parse table name before it
is passed to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9820#issuecomment-157905536
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/9820#issuecomment-157905534
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 felixcheung commented on the pull request:
https://github.com/apache/spark/pull/9785#issuecomment-157862641
@shivaram agreed completely.
Should we merge this then? I could open JIRA for `sample, table, cov`
---
If your project is set up for it, you can reply to this
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9705#issuecomment-157862906
Merged into master and branch-1.6. Thanks!
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9705
---
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9805#issuecomment-157863731
**[Test build #46238 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46238/consoleFull)**
for PR 9805 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9817#issuecomment-157863909
**[Test build #46240 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46240/consoleFull)**
for PR 9817 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9805#issuecomment-157863927
Test PASSed.
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/9805#issuecomment-157863926
Merged build finished. Test PASSed.
---
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/9773#issuecomment-157863980
**[Test build #46242 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46242/consoleFull)**
for PR 9773 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9817#issuecomment-157864080
Merged build finished. Test PASSed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9817#issuecomment-157864082
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9814
---
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
Github user vundela commented on a diff in the pull request:
https://github.com/apache/spark/pull/9809#discussion_r45260699
--- Diff:
core/src/main/scala/org/apache/spark/util/SparkUncaughtExceptionHandler.scala
---
@@ -46,6 +46,18 @@ private[spark] object
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9798#issuecomment-157864689
`testEstimatorAndModelReadWrite` calls `fit`, which takes some extra time.
So I construct the model directly.
---
If your project is set up for it, you can reply to
Github user huaxingao commented on the pull request:
https://github.com/apache/spark/pull/9773#issuecomment-157865029
I will add a test case.
---
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
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/spark/pull/9812#discussion_r45260904
--- Diff: core/src/main/scala/org/apache/spark/TestUtils.scala ---
@@ -159,6 +159,16 @@ private[spark] object TestUtils {
Github user HeartSaVioR commented on a diff in the pull request:
https://github.com/apache/spark/pull/9812#discussion_r45261349
--- Diff:
repl/src/main/scala/org/apache/spark/repl/ExecutorClassLoader.scala ---
@@ -55,6 +57,14 @@ class ExecutorClassLoader(conf: SparkConf, classUri:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9815#issuecomment-157866014
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/9774#issuecomment-157865900
**[Test build #46244 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46244/consoleFull)**
for PR 9774 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9786#issuecomment-157865923
LGTM2. Merged into master and branch-1.6. Thanks!
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9815#issuecomment-157866017
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9786
---
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
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9656#issuecomment-157867300
@fayeshine #9814 was merged. Do you mind closing this PR manually? Thanks
for your contribution!
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9795#issuecomment-157867436
**[Test build #46230 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46230/consoleFull)**
for PR 9795 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9795#issuecomment-157867814
Merged build finished. Test PASSed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9795#issuecomment-157867819
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
GitHub user hvanhovell opened a pull request:
https://github.com/apache/spark/pull/9819
[SPARK-8641][SQL] Native Spark Window functions
This PR removes Hive windows functions from Spark and replaces them with
(native) Spark ones. The PR is on par with Hive in terms of features.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9809#issuecomment-157868087
**[Test build #46229 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46229/consoleFull)**
for PR 9809 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9809#issuecomment-157868385
Merged build finished. Test PASSed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9809#issuecomment-157868390
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9803
---
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
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/9775#issuecomment-157869594
@dtolpin could you add a summary to the PR title?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5423#issuecomment-157870208
**[Test build #46226 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/46226/consoleFull)**
for PR 5423 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9809#issuecomment-157869944
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9809#issuecomment-157869946
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/5423#issuecomment-157870306
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/9803#issuecomment-157870370
It is a good practice in Spark to mark variable `transient` if we know they
are not used remotely. It is tricky to avoid serialize the entire class into a
closure
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5423#issuecomment-157870307
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/9727
---
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
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9727#issuecomment-157870829
LGTM. Merged into master and branch-1.6. Thanks!
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9798#issuecomment-157871288
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/9811#issuecomment-157871321
LGTM. Merged into master and branch-1.6. Thanks!
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9798#issuecomment-157871284
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/9811
---
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
901 - 961 of 961 matches
Mail list logo
