Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12224#issuecomment-209147703
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/12342#discussion_r59471369
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -898,7 +896,7 @@ object PruneFilters extends
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12224#issuecomment-209147702
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/12224#issuecomment-209147695
**[Test build #55664 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55664/consoleFull)**
for PR 12224 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12342#issuecomment-209147366
**[Test build #55663 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55663/consoleFull)**
for PR 12342 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12224#issuecomment-209147392
**[Test build #55664 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55664/consoleFull)**
for PR 12224 at commit
Github user davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/12342#discussion_r59470693
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -915,41 +913,7 @@ object PushPredicateThroughProject
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12342#issuecomment-209146531
**[Test build #55662 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55662/consoleFull)**
for PR 12342 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12342#issuecomment-209146107
cc @marmbrus @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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12304#issuecomment-209145959
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 davies opened a pull request:
https://github.com/apache/spark/pull/12342
[SPARK-14581] [SQL] push predicatese through more logical plans
## What changes were proposed in this pull request?
Right now, filter push down only works with Project, Aggregate, Generate
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12304#issuecomment-209145914
**[Test build #55661 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55661/consoleFull)**
for PR 12304 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12304#issuecomment-209145962
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/12285#issuecomment-209145062
Merged into master and 1.6 branch (fixed the conflicts)
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/12285
---
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/12304#issuecomment-209143266
**[Test build #55661 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55661/consoleFull)**
for PR 12304 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/12339#issuecomment-209137303
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 this
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12224#issuecomment-209141072
**[Test build #55660 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55660/consoleFull)**
for PR 12224 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12224#issuecomment-209141096
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/12224#issuecomment-209141088
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 BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/12304#issuecomment-209140575
I made that change and fixed the comments in util.py
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12224#issuecomment-209140204
**[Test build #55660 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55660/consoleFull)**
for PR 12224 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12339#issuecomment-209140211
**[Test build #55659 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55659/consoleFull)**
for PR 12339 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12285#issuecomment-209136475
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 holdenk commented on the pull request:
https://github.com/apache/spark/pull/9008#issuecomment-209136374
@sethah So to avoid adding any overhead from computing stats for both these
params one option would be to selectively compute only the stats that are
required (e.g. if
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12285#issuecomment-209136477
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/12285#issuecomment-209136189
**[Test build #55646 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55646/consoleFull)**
for PR 12285 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12331#issuecomment-209136066
Done with review pass
---
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 jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/12331#discussion_r59468142
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LogisticRegression.scala
---
@@ -273,6 +273,10 @@ class LogisticRegression
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/12331#discussion_r59468170
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/util/Instrumentation.scala ---
@@ -0,0 +1,109 @@
+/*
+ * Licensed to the Apache Software
Github user bomeng commented on a diff in the pull request:
https://github.com/apache/spark/pull/12314#discussion_r59468158
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/NoSuchItemException.scala
---
@@ -17,36 +17,21 @@
package
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/12331#discussion_r59468154
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/util/Instrumentation.scala ---
@@ -0,0 +1,109 @@
+/*
+ * Licensed to the Apache Software
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12331#issuecomment-209135999
Should we change all existing logging messages in LogisticRegression to use
Instrumentation?
---
If your project is set up for it, you can reply to this email and
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/12331#discussion_r59468159
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/util/Instrumentation.scala ---
@@ -0,0 +1,109 @@
+/*
+ * Licensed to the Apache Software
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/12331#discussion_r59468156
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/util/Instrumentation.scala ---
@@ -0,0 +1,109 @@
+/*
+ * Licensed to the Apache Software
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/12331#discussion_r59468146
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/util/Instrumentation.scala ---
@@ -0,0 +1,109 @@
+/*
+ * Licensed to the Apache Software
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/12331#discussion_r59468165
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/util/Instrumentation.scala ---
@@ -0,0 +1,109 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-209135892
**[Test build #55658 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55658/consoleFull)**
for PR 12271 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-209135567
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/12271#issuecomment-209135570
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/12339#issuecomment-209134638
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/12339#issuecomment-209134639
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/12339#issuecomment-209134603
**[Test build #55653 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55653/consoleFull)**
for PR 12339 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12340#issuecomment-209133718
**[Test build #55657 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55657/consoleFull)**
for PR 12340 at commit
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12340#issuecomment-209133359
Rebased to trigger Jenkins again.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12157#issuecomment-209133453
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/12157#issuecomment-209133450
**[Test build #55656 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55656/consoleFull)**
for PR 12157 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12157#issuecomment-209133455
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user BryanCutler commented on the pull request:
https://github.com/apache/spark/pull/12304#issuecomment-209133034
I was thinking that the other classes, like `JavaModel`, actually wrap that
object so I used a slightly different name - but I agree, `JavaParams` sounds
much
Github user kevincox commented on a diff in the pull request:
https://github.com/apache/spark/pull/12337#discussion_r59466558
--- Diff: python/pyspark/sql/functions.py ---
@@ -138,6 +138,10 @@ def _():
' eliminated.'
}
+_functions_1_8 = {
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/12331#issuecomment-209132617
I'll take a look
---
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 bomeng commented on a diff in the pull request:
https://github.com/apache/spark/pull/12314#discussion_r59466520
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -29,6 +29,7 @@ import
Github user dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12340#issuecomment-209132312
Amazing. There must be some problem in Jenkins server. It's JVM error.
```
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option
MaxPermSize=512m;
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12157#issuecomment-209132168
**[Test build #55656 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55656/consoleFull)**
for PR 12157 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12341#issuecomment-209132023
Can one of the admins verify this patch?
---
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 seyfe opened a pull request:
https://github.com/apache/spark/pull/12341
[SPARK-14576] [Web UI] Spark console should display Web UI url
## What changes were proposed in this pull request?
This is a proposal to print the Spark Driver UI link when spark-shell is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12340#issuecomment-209130627
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/12340#issuecomment-209130615
**[Test build #55655 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55655/consoleFull)**
for PR 12340 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12340#issuecomment-209130625
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/12340#issuecomment-209129813
**[Test build #55655 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55655/consoleFull)**
for PR 12340 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/12315
---
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 dongjoon-hyun commented on the pull request:
https://github.com/apache/spark/pull/12340#issuecomment-209128788
Hi, @rxin .
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 dongjoon-hyun opened a pull request:
https://github.com/apache/spark/pull/12340
[SPARK-14580][SQL] Hive IfCoercion should preserve predicate.
## What changes were proposed in this pull request?
Currently, `HiveTypeCoercion.IfCoercion` removes all predicates
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12271#issuecomment-209128481
**[Test build #55654 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55654/consoleFull)**
for PR 12271 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/12339#issuecomment-209128576
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/12315#issuecomment-209128553
Alright going to merge this.
---
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/9524#issuecomment-209127890
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/9524#issuecomment-209127888
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/9524#issuecomment-209127585
**[Test build #55641 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55641/consoleFull)**
for PR 9524 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12315#issuecomment-209126682
**[Test build #2780 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2780/consoleFull)**
for PR 12315 at commit
Github user zsxwing commented on the pull request:
https://github.com/apache/spark/pull/12339#issuecomment-209126318
cc @marmbrus
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12336#issuecomment-209126053
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/12336#issuecomment-209126016
**[Test build #55652 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55652/consoleFull)**
for PR 12336 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12336#issuecomment-209126055
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user zsxwing commented on a diff in the pull request:
https://github.com/apache/spark/pull/12339#discussion_r59463681
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/streaming/StreamExecution.scala
---
@@ -228,7 +231,7 @@ class StreamExecution(
*
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12339#issuecomment-209125207
**[Test build #55653 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55653/consoleFull)**
for PR 12339 at commit
Github user nchammas commented on the pull request:
https://github.com/apache/spark/pull/8318#issuecomment-209125293
No worries. I just wanted to make sure that the idea was sound since there
were concerns early on about whether we should even try to package PySpark
independently.
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/12339
Fix a race condition in StreamExecution.processAllAvailable
## What changes were proposed in this pull request?
There is a race condition in `StreamExecution.processAllAvailable`. Here is
Github user thunterdb commented on the pull request:
https://github.com/apache/spark/pull/12331#issuecomment-209124853
cc @mengxr
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/12311
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/12311#issuecomment-209122458
Merging this into master, 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
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/12333#issuecomment-209122343
@dhruve you should put the jira name int he pr description.
Please see guidelines at:
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/12333#issuecomment-209121895
So I agree its not explicitly necessary to state Xms here, the only reason
I think to mention it is the behavior is different from 1.X to 2.X, but there
will be many
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12311#issuecomment-209121227
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/12311#issuecomment-209121226
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/12338#issuecomment-209120418
**[Test build #55651 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55651/consoleFull)**
for PR 12338 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12336#issuecomment-209120398
**[Test build #55652 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55652/consoleFull)**
for PR 12336 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12311#issuecomment-209120431
**[Test build #55638 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55638/consoleFull)**
for PR 12311 at commit
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/12338#issuecomment-209119089
cc @marmbrus @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
GitHub user davies opened a pull request:
https://github.com/apache/spark/pull/12338
[SPARK-14578] [SQL] Fix codegen for CreateExternalRow with nested wide
schema
## What changes were proposed in this pull request?
The wide schema, the expression of fields will be splitted
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/12337#discussion_r59461131
--- Diff: python/pyspark/sql/functions.py ---
@@ -138,6 +138,10 @@ def _():
' eliminated.'
}
+_functions_1_8 = {
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/8318#issuecomment-209116066
I'm do not have bandwidth to work on this (also don't think this is high
priority), someone could take over this to move forward.
---
If your project is set up for it,
Github user sitalkedia commented on the pull request:
https://github.com/apache/spark/pull/12285#issuecomment-209115656
Thanks a lot for your quick review and response :).
---
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/12332#issuecomment-209115525
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/12314#discussion_r59459447
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/ddl.scala ---
@@ -29,6 +29,7 @@ import
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12336#issuecomment-209115424
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/12336#issuecomment-209115382
**[Test build #55648 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55648/consoleFull)**
for PR 12336 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12336#issuecomment-209115429
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/12332#issuecomment-209115523
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 davies commented on the pull request:
https://github.com/apache/spark/pull/12285#issuecomment-209115364
LGTM, will merging once passing the tests. Thanks for working on it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
201 - 300 of 740 matches
Mail list logo
