Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/13210#discussion_r63988091
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/UnsupportedOperationChecker.scala
---
@@ -55,10 +55,19 @@ object
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 tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/13210#discussion_r63987926
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/UnsupportedOperationChecker.scala
---
@@ -55,10 +55,19 @@ object
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/8648
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/13089
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/11915
---
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 jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/13210#discussion_r63987729
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/UnsupportedOperationChecker.scala
---
@@ -55,10 +55,19 @@ object
Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/13210#discussion_r63987696
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/UnsupportedOperationChecker.scala
---
@@ -55,10 +55,19 @@ object
Github user jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/13210#discussion_r63987667
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/UnsupportedOperationChecker.scala
---
@@ -55,10 +55,19 @@ object
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13101
---
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/13101#issuecomment-220509850
Merged into master and branch-2.0. 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 kiszk commented on a diff in the pull request:
https://github.com/apache/spark/pull/13204#discussion_r63987521
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/WholeStageCodegenExec.scala
---
@@ -247,9 +247,7 @@ case class InputAdapter(child:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220509745
**[Test build #3002 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3002/consoleFull)**
for PR 12932 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13207#issuecomment-220509434
**[Test build #3001 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3001/consoleFull)**
for PR 13207 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13210#issuecomment-220509194
**[Test build #58936 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58936/consoleFull)**
for PR 13210 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220508703
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/13200#issuecomment-220508705
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/13207#issuecomment-220508699
**[Test build #3000 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3000/consoleFull)**
for PR 13207 at commit
GitHub user tdas opened a pull request:
https://github.com/apache/spark/pull/13210
SPARK-15428
## What changes were proposed in this pull request?
Incrementalizing plans of with multiple streaming aggregation is tricky and
we dont have the necessary support for "delta" to
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220508596
**[Test build #58931 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58931/consoleFull)**
for PR 13200 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13188#issuecomment-220507832
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 smungee commented on the pull request:
https://github.com/apache/spark/pull/13108#issuecomment-220507839
@rxin The code in question seems to have been removed in this commit by
@cloud-fan
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13188#issuecomment-220507731
**[Test build #58926 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58926/consoleFull)**
for PR 13188 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13156#issuecomment-220507235
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/13208#issuecomment-220507260
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/13208#issuecomment-220507261
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/13156#issuecomment-220507239
Test FAILed.
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/13156#issuecomment-220507152
**[Test build #58934 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58934/consoleFull)**
for PR 13156 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13208#issuecomment-220507143
**[Test build #58927 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58927/consoleFull)**
for PR 13208 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12772#issuecomment-220507084
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/12772#issuecomment-220507082
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/12772#issuecomment-220506991
**[Test build #58932 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58932/consoleFull)**
for PR 12772 at commit
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 davies commented on the pull request:
https://github.com/apache/spark/pull/13204#issuecomment-220505833
@yucai Yes, corrected, 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 project does not
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 yucai commented on the pull request:
https://github.com/apache/spark/pull/13204#issuecomment-220505548
Hi Davis,
In your comments "Hopefully we do need to pay much attention on this", do
you mean "we do not need to pay much attention..."?
---
If your project is
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/13188#issuecomment-220505375
Could you remove ss_max, otherwise LGTM
---
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/13188#discussion_r63985324
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/benchmark/tpcds/TPCDSQueryBenchmark.scala
---
@@ -0,0 +1,132 @@
+/*
+ * Licensed to
Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/13193#issuecomment-220505260
@rxin Thank you, I removed [MINOR] from 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 your
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/9759#issuecomment-220504947
For 2.7.4, jackson-module-scala_2.11:2.7.4 seems not released on mvn repo.
So it causes unresolved dependencies when building.
---
If your project is set up for it,
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13207#issuecomment-220504787
Any idea why the test would fail this way?
---
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/12932#issuecomment-220504635
**[Test build #2998 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2998/consoleFull)**
for PR 12932 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 viirya commented on the pull request:
https://github.com/apache/spark/pull/9759#issuecomment-220504278
For jackson-databind:
+-com.fasterxml.jackson.core:jackson-databind:2.3.1 (evicted by: 2.7.3)
...
| +-com.fasterxml.jackson.core:jackson-databind:2.4.2
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220503868
**[Test build #3002 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3002/consoleFull)**
for PR 12932 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13193#issuecomment-220503830
Maybe remove MINOR from 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 your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13206#issuecomment-220503826
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/13206#issuecomment-220503827
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/13207#issuecomment-220503805
**[Test build #2997 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2997/consoleFull)**
for PR 13207 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13206#issuecomment-220503694
**[Test build #58925 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58925/consoleFull)**
for PR 13206 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13193#issuecomment-220503555
cc @sameeragarwal for review
---
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 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220503327
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/12932#issuecomment-220503326
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 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/12932#issuecomment-220503213
**[Test build #58930 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58930/consoleFull)**
for PR 12932 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13087#issuecomment-220503129
cc @cloud-fan
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13188#issuecomment-220503070
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/13188#issuecomment-220503069
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/13188#issuecomment-220502933
**[Test build #58922 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58922/consoleFull)**
for PR 13188 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/13203#issuecomment-220502494
LGTM
---
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
Github user linbojin commented on the pull request:
https://github.com/apache/spark/pull/13087#issuecomment-220502400
Hi, @marmbrus
Could you review this PR?
---
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/13101#issuecomment-220502372
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/13101#issuecomment-220502374
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/13101#issuecomment-220502291
**[Test build #58929 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58929/consoleFull)**
for PR 13101 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13170#issuecomment-220501865
**[Test build #58935 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58935/consoleFull)**
for PR 13170 at commit
Github user wangyang1992 commented on the pull request:
https://github.com/apache/spark/pull/13177#issuecomment-220501798
@andrewor14 Thanks :-). Do I still need to modify the code? Frankly, I
don't really understand your comment above. ("this won't actually work because
it'll find
Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/13170#issuecomment-220501720
@hvanhovell Thanks. I have address your comments.
---
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/13101#issuecomment-220501406
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/13101#issuecomment-220501409
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/13101#issuecomment-220501338
**[Test build #58928 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58928/consoleFull)**
for PR 13101 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13101#issuecomment-220500920
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/13101#issuecomment-220500923
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/13101#issuecomment-220500757
**[Test build #58923 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58923/consoleFull)**
for PR 13101 at commit
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13156#issuecomment-220500710
**[Test build #58934 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58934/consoleFull)**
for PR 13156 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/12932#issuecomment-220500453
We should backport this into 1.6 as well.
---
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 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
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/13156#issuecomment-220500330
retest this please
---
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 koertkuipers closed the pull request at:
https://github.com/apache/spark/pull/11980
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220499665
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/13200#issuecomment-220499663
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/13200#issuecomment-220499533
**[Test build #58921 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58921/consoleFull)**
for PR 13200 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12772#issuecomment-220499461
**[Test build #58932 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58932/consoleFull)**
for PR 12772 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13207#issuecomment-220499268
**[Test build #3001 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3001/consoleFull)**
for PR 13207 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/12772#issuecomment-220499145
ok to 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 feature
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220499040
I updated Python docs. The Python change seems slightly larger and since it
is not user facing, I'm going to defer it to another pr.
---
If your project is set up for
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13207#issuecomment-220498876
**[Test build #3000 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/3000/consoleFull)**
for PR 13207 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/13207#issuecomment-220498914
tes this please
---
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/13200#issuecomment-220498825
**[Test build #58931 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58931/consoleFull)**
for PR 13200 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13207#issuecomment-220498546
**[Test build #2996 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2996/consoleFull)**
for PR 13207 at commit
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/13101#issuecomment-220497757
LGTM pending Jenkins
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/13130#issuecomment-220497728
Do you know why it OOMs when it is softValues?
---
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 DoingDone9 commented on the pull request:
https://github.com/apache/spark/pull/13130#issuecomment-220497354
cc @yhuai @srowen
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13101#issuecomment-220497096
**[Test build #58929 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/58929/consoleFull)**
for PR 13101 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13200#issuecomment-220497122
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/13200#issuecomment-220497120
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
101 - 200 of 811 matches
Mail list logo
