Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/4252#issuecomment-71927775
Hey @pwendell,
Just remembered that there's an extra bit that needs to be taken care of
when shading. `core/pom.xml` has a `copy-dependencies` task to copy
Github user javadba commented on a diff in the pull request:
https://github.com/apache/spark/pull/4254#discussion_r23728761
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/clustering/PIClustering.scala ---
@@ -0,0 +1,433 @@
+/*
+ * Licensed to the Apache Software
Github user javadba commented on a diff in the pull request:
https://github.com/apache/spark/pull/4254#discussion_r23728918
--- Diff: mllib/src/test/resources/log4j.mllib.properties ---
@@ -0,0 +1,41 @@
+#
--- End diff --
OK
---
If your project is set up for it,
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/4047#discussion_r23729109
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/clustering/LDA.scala
---
@@ -0,0 +1,472 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/3798#discussion_r23729113
--- Diff:
external/kafka/src/main/scala/org/apache/spark/streaming/kafka/KafkaUtils.scala
---
@@ -144,4 +150,116 @@ object KafkaUtils {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4120#issuecomment-71929366
[Test build #26259 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26259/consoleFull)
for PR 4120 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4215#issuecomment-71929299
[Test build #26258 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26258/consoleFull)
for PR 4215 at commit
Github user freeman-lab commented on the pull request:
https://github.com/apache/spark/pull/3803#issuecomment-71929328
Great thanks @JoshRosen will finish this up ASAP!
---
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/3571#issuecomment-71929324
[Test build #26260 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26260/consoleFull)
for PR 3571 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4137#issuecomment-71933280
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/4137#issuecomment-71933270
[Test build #26249 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26249/consoleFull)
for PR 4137 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/4047#issuecomment-71934257
@EntilZha I'll see about merging my testing branch back into this now,
though it's not quite ready yet b/c of issues with checkpointing:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4241#issuecomment-71934459
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/4241#issuecomment-71934451
[Test build #26251 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26251/consoleFull)
for PR 4241 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4215#issuecomment-71935867
[Test build #26255 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26255/consoleFull)
for PR 4215 at commit
Github user liyezhang556520 closed the pull request at:
https://github.com/apache/spark/pull/3970
---
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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/4228#discussion_r23740428
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -901,6 +901,38 @@ abstract class RDD[T: ClassTag](
}
/**
+ *
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4006#issuecomment-71955607
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/4006#issuecomment-71955606
[Test build #26279 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26279/consoleFull)
for PR 4006 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4006#issuecomment-71955528
[Test build #26279 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26279/consoleFull)
for PR 4006 at commit
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/4014#issuecomment-71956530
Can you explain in the PR what is schema-less delimiter?
---
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/4006#issuecomment-71956401
[Test build #26280 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26280/consoleFull)
for PR 4006 at commit
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/4228#issuecomment-71957158
@mengxr makes sense
---
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 tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/3798#discussion_r23743753
--- Diff:
external/kafka/src/main/scala/org/apache/spark/rdd/kafka/KafkaCluster.scala ---
@@ -0,0 +1,320 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4259#issuecomment-71963887
[Test build #26283 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26283/consoleFull)
for PR 4259 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4260#issuecomment-71963926
[Test build #26285 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26285/consoleFull)
for PR 4260 at commit
GitHub user tmyklebu opened a pull request:
https://github.com/apache/spark/pull/4261
A JDBC driver for Spark SQL.
This pull request contains a Spark SQL data source that can pull data from,
and can put data into, a JDBC database.
I have tested both read and write support
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4261#issuecomment-71964607
[Test build #26286 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26286/consoleFull)
for PR 4261 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4261#issuecomment-71964610
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/4261#issuecomment-71964600
[Test build #26286 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26286/consoleFull)
for PR 4261 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4260#issuecomment-71963928
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/4258#issuecomment-71964178
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/4254#issuecomment-71965181
[Test build #26282 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26282/consoleFull)
for PR 4254 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4254#issuecomment-71965185
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/4260#issuecomment-71965288
[Test build #26287 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26287/consoleFull)
for PR 4260 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4261#issuecomment-71966019
[Test build #26288 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26288/consoleFull)
for PR 4261 at commit
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/4248#issuecomment-71966684
Jenkins, 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
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/4248#issuecomment-7199
I was confused here whether to use manual clock or system clock ? Since
system clock made the test considerably faster. P.S. Test failures seems to
be
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4248#issuecomment-71966791
[Test build #26289 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26289/consoleFull)
for PR 4248 at commit
Github user adrian-wang commented on the pull request:
https://github.com/apache/spark/pull/4057#issuecomment-71967465
@yhuai Thanks for your comments! I'll modify this PR accordingly.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4068#issuecomment-71967503
[Test build #26290 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26290/consoleFull)
for PR 4068 at commit
Github user koeninger commented on a diff in the pull request:
https://github.com/apache/spark/pull/3798#discussion_r23746235
--- Diff:
external/kafka/src/main/scala/org/apache/spark/rdd/kafka/OffsetRange.scala ---
@@ -0,0 +1,70 @@
+/*
+ * Licensed to the Apache Software
Github user koeninger commented on a diff in the pull request:
https://github.com/apache/spark/pull/3798#discussion_r23746262
--- Diff:
external/kafka/src/main/scala/org/apache/spark/streaming/kafka/KafkaUtils.scala
---
@@ -144,4 +150,116 @@ object KafkaUtils {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4256#issuecomment-71953603
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/4256#issuecomment-71953597
[Test build #26270 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26270/consoleFull)
for PR 4256 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/4234#issuecomment-71953824
OK, like add some `count()` calls to make it persist the RDDs? or just
treat this as wont-fix?
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4257#issuecomment-71953996
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 ankurdave commented on the pull request:
https://github.com/apache/spark/pull/4234#issuecomment-71953568
@srowen Caching here is necessary since we do reuse some uncached datasets,
so I don't think there's a good solution for uncaching in this kind of
situation.
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4256#issuecomment-71953573
[Test build #26276 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26276/consoleFull)
for PR 4256 at commit
GitHub user KaiXinXiaoLei opened a pull request:
https://github.com/apache/spark/pull/4257
Add a config option to print DAG.
Add a config option spark.rddDebug.enable to check whether to print DAG
info. When spark.rddDebug.enable is true, it will print information about DAG
in the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4215#issuecomment-71955530
[Test build #26277 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26277/consoleFull)
for PR 4215 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4256#issuecomment-71955527
[Test build #26278 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26278/consoleFull)
for PR 4256 at commit
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/4198#issuecomment-71957049
Thanks @smarthi !
---
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 viirya commented on the pull request:
https://github.com/apache/spark/pull/4014#issuecomment-71957621
[Schema-less Map-reduce
Scripts](https://cwiki.apache.org/confluence/display/Hive/LanguageManual+Transform#LanguageManualTransform-Schema-lessMap-reduceScripts)
is a
Github user jinntrance commented on a diff in the pull request:
https://github.com/apache/spark/pull/4247#discussion_r23744568
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/feature/Word2Vec.scala ---
@@ -290,111 +290,126 @@ class Word2Vec extends Serializable with Logging
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4006#issuecomment-71962481
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/4006#issuecomment-71962472
[Test build #26280 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26280/consoleFull)
for PR 4006 at commit
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/4223#issuecomment-71963599
The root cause is likely you aren't using the right version of hive.
Where right means our hacked version that has a version of kryo that doesn't
conflict with spark.
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/4260
[SQL] Various DataFrame DSL update.
1. Added foreach, foreachPartition, flatMap to DataFrame.
2. Added col() in dsl.
3. Support renaming columns in toDataFrame.
4. Support type inference on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4259#issuecomment-71961789
[Test build #26284 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26284/consoleFull)
for PR 4259 at commit
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/3833#discussion_r23743161
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/optimization/Gradient.scala ---
@@ -55,24 +57,79 @@ abstract class Gradient extends Serializable {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4256#issuecomment-71959946
[Test build #26276 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26276/consoleFull)
for PR 4256 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4241
---
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/4258#issuecomment-71958741
[Test build #26281 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26281/consoleFull)
for PR 4258 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4256#issuecomment-71961728
[Test build #26278 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26278/consoleFull)
for PR 4256 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4259#issuecomment-71960804
[Test build #26283 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26283/consoleFull)
for PR 4259 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4241#issuecomment-71961604
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/4260#issuecomment-71963705
cc @mengxr for mllib changes
---
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/4223#issuecomment-71963496
I am going to let @marmbrus to comment on this one ...
---
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/4259#issuecomment-71961315
[Test build #26284 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26284/consoleFull)
for PR 4259 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4241#issuecomment-71961595
[Test build #26275 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26275/consoleFull)
for PR 4241 at commit
Github user zzcclp commented on the pull request:
https://github.com/apache/spark/pull/4258#issuecomment-71959063
LGTM, I test this with spark-branch 1.2, it works correctly. :)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
GitHub user lianhuiwang opened a pull request:
https://github.com/apache/spark/pull/4258
[SPARK-5470][Core]use defaultClassLoader to load classes of
classesToRegister in KryoSeria...
Now KryoSerializer load classes of classesToRegister at the time of its
initialization. when we
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4259#issuecomment-71961793
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/4256#issuecomment-71959952
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/3798#discussion_r23742746
--- Diff:
external/kafka/src/main/scala/org/apache/spark/streaming/kafka/KafkaUtils.scala
---
@@ -144,4 +150,116 @@ object KafkaUtils {
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4260#issuecomment-71963853
[Test build #26285 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26285/consoleFull)
for PR 4260 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4259#issuecomment-71963892
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/4241#issuecomment-71960238
[Test build #26274 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26274/consoleFull)
for PR 4241 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4241#issuecomment-71960243
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/4256#issuecomment-71961733
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user tdas commented on a diff in the pull request:
https://github.com/apache/spark/pull/3798#discussion_r23743523
--- Diff:
external/kafka/src/test/scala/org/apache/spark/streaming/kafka/KafkaStreamSuite.scala
---
@@ -130,7 +130,7 @@ abstract class KafkaStreamSuiteBase
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/3798#issuecomment-71960076
At a high level these are the high level design issues that are still
pending
- Packaging - I think all the classes should be
org.apache.spark.streaming.kafka
GitHub user dbtsai opened a pull request:
https://github.com/apache/spark/pull/4259
[SPARK-5253] [ML] LinearRegression with L1/L2 (ElasticNet) using OWLQN
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/AlpineNow/spark lir
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4215#issuecomment-71960138
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/4254#issuecomment-71959963
[Test build #26282 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26282/consoleFull)
for PR 4254 at commit
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/3833#discussion_r23743197
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/optimization/Gradient.scala ---
@@ -55,24 +57,79 @@ abstract class Gradient extends Serializable {
Github user mccheah commented on a diff in the pull request:
https://github.com/apache/spark/pull/4155#discussion_r23743012
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/OutputCommitCoordinator.scala ---
@@ -0,0 +1,258 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4258#issuecomment-71964173
[Test build #26281 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26281/consoleFull)
for PR 4258 at commit
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/4155#discussion_r23742870
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/OutputCommitCoordinator.scala ---
@@ -0,0 +1,258 @@
+/*
+ * Licensed to the Apache
Github user viirya commented on the pull request:
https://github.com/apache/spark/pull/4223#issuecomment-71958179
@rxin This is a quick fix for the problem when generating Hive golden
answer files on Hive 0.13.1. Do not know if it is useful for others. It would
be great if you can
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/3798#issuecomment-71960172
Jenkins, this is okay 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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4215#issuecomment-71960123
[Test build #26277 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26277/consoleFull)
for PR 4215 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/4241#issuecomment-71951941
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/4241#issuecomment-71952029
[Test build #26274 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26274/consoleFull)
for PR 4241 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2429#issuecomment-71951971
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4241#issuecomment-71951933
[Test build #26264 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26264/consoleFull)
for PR 4241 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/4228
---
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/4228#issuecomment-71952501
Merged into master. @sryza I kept the current `treeAggregate`/`treeReduce`
names. Please check my inline comments about overloading `aggregate`.
---
If your project is
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/4241#issuecomment-71952548
[Test build #26275 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/26275/consoleFull)
for PR 4241 at commit
401 - 500 of 713 matches
Mail list logo
