Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1220
---
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 markhamstra closed the pull request at:
https://github.com/apache/spark/pull/686
---
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 AnkitBhardwaj12 opened a pull request:
https://github.com/apache/spark/pull/1298
Bounded priority queue and kryo issue
[SPARK-2306] : BoundedPriorityQueue is private and not registered with Kryo
Due to the non registration of BoundedPriorityQueue in kryo ,RDD.Top is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1294#issuecomment-48013021
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1294#issuecomment-48013022
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16336/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1298#issuecomment-48013147
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1294#issuecomment-48013186
Thanks. I'm merging this in master and branch-1.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1294
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1265#issuecomment-48013259
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1265#issuecomment-48013386
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1265#issuecomment-48013380
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1298#issuecomment-48013459
I don't think you meant to bring in so many commits. Can you fix that?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AnkitBhardwaj12 closed the pull request at:
https://github.com/apache/spark/pull/1298
---
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 AnkitBhardwaj12 opened a pull request:
https://github.com/apache/spark/pull/1299
[SPARK-2306]:BoundedPriorityQueue is private and not registered with Kry...
Due to the non registration of BoundedPriorityQueue with kryoserializer,
operations which are dependend on
Github user AnkitBhardwaj12 commented on the pull request:
https://github.com/apache/spark/pull/1298#issuecomment-48014809
Sorry for that created a new pull request with single file commit.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1272#issuecomment-48015480
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1272#issuecomment-48015483
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16338/
---
If your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1272
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1272#issuecomment-48015592
Thanks. I'm merging this in master branch-1.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1299#issuecomment-48015651
Jenkins, test 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1299#issuecomment-48015943
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/906#issuecomment-48016357
Build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1300#issuecomment-48016602
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1300#issuecomment-48016595
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1265#issuecomment-48017381
Ok looks like those two tests are now passing. I'm merging this in master
branch-1.0.
---
If your project is set up for it, you can reply to this email and have your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1265
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/906#issuecomment-48018918
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1265#issuecomment-48019489
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16340/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1299#issuecomment-48019490
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16341/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1299#issuecomment-48019487
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1300#issuecomment-48020043
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16342/
---
If your
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/1291#issuecomment-48020036
It makes sense for the problem you addressed, but modified in
`ShuffleDStream` seems like just a workaround method, not a good solution,
since you may also face this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1300#issuecomment-48020042
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1301#issuecomment-48021273
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1301#issuecomment-48021268
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/964#issuecomment-48023068
@vrilleup treeAggregate: https://github.com/apache/spark/pull/1110
@yangliuyu Could you confirm `userSize = 10`?
---
If your project is set up for it, you can
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/1212#discussion_r14552579
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -431,6 +442,10 @@ private[spark] class TaskSchedulerImpl(
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/1212#discussion_r14552666
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSchedulerImpl.scala ---
@@ -431,6 +442,10 @@ private[spark] class TaskSchedulerImpl(
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/1212#issuecomment-48024156
Looks good, thanks !
Please add a specific testcase which tests the change in behavior : namely,
what used to be ANY schedule earlier is not RACK_LOCAL.
---
If your
Github user lirui-intel commented on the pull request:
https://github.com/apache/spark/pull/1212#issuecomment-48025283
Thanks @mridulm for the review!
I don't quite get your point about the testcase though, could you please be
more specific on what testcase should be added?
---
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1151
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1150#issuecomment-48026526
This is conflicting now that we merged the other PR.
test this please
---
If your project is set up for it, you can reply to this email and have your
reply
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1150#discussion_r14553914
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -623,6 +623,8 @@ private[hive] object HiveQl {
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1150#discussion_r14553945
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -205,3 +205,15 @@ object ExistingRdd {
case class
Github user YanjieGao commented on a diff in the pull request:
https://github.com/apache/spark/pull/1150#discussion_r14553981
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/basicOperators.scala ---
@@ -205,3 +205,15 @@ object ExistingRdd {
case class
Github user YanjieGao commented on a diff in the pull request:
https://github.com/apache/spark/pull/1150#discussion_r14553975
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/HiveQl.scala ---
@@ -623,6 +623,8 @@ private[hive] object HiveQl {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1301#issuecomment-48028941
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16344/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1301#issuecomment-48028940
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user YanjieGao commented on a diff in the pull request:
https://github.com/apache/spark/pull/1150#discussion_r14555293
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -274,7 +274,7 @@ private[sql] abstract class SparkStrategies
Github user YanjieGao commented on the pull request:
https://github.com/apache/spark/pull/1150#issuecomment-48030332
Hi Michael,I have resolve the conflict .
---
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 ngbinh opened a pull request:
https://github.com/apache/spark/pull/1302
SPARK-2367: update io.netty from 4.0.17 to 4.0.21
pretty big performance improvement and some bug fixes.
More details: http://netty.io/news/2014/07/01/4.html
You can merge this pull request into
GitHub user ngbinh opened a pull request:
https://github.com/apache/spark/pull/1303
SPARK-2368 Making FileServerHandler sends gracefully to prevent OOM
Busy wait for the channel to be ready before writing to it to prevent
the buffer from exploding.
Also making some
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1303#issuecomment-48033290
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1303#issuecomment-48033304
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1302#issuecomment-48033303
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1155#issuecomment-48034013
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1302#issuecomment-48034018
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1155#issuecomment-48034005
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1302#issuecomment-48034019
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16346/
---
If your project is set up for it, you can
Github user avulanov commented on the pull request:
https://github.com/apache/spark/pull/1155#issuecomment-48035031
@mengxr Thanks for your review! I've addressed all suggestions, except: 1)I
used Experimental annotation for the whole class only. Do I need to annotate
each method?
Github user yangliuyu commented on the pull request:
https://github.com/apache/spark/pull/964#issuecomment-48037519
@mengxr yes, userSize is 10
---
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 witgo commented on the pull request:
https://github.com/apache/spark/pull/1302#issuecomment-48038212
Run some simple tasks, there seems to be no problem.
Jenkins, test this please.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/1303#discussion_r14558471
--- Diff:
core/src/main/java/org/apache/spark/network/netty/FileServerHandler.java ---
@@ -80,4 +78,11 @@ public void exceptionCaught(ChannelHandlerContext
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/1303#issuecomment-48041294
The config changes look promising (btw, you will need to read them from
SparkConf and not hardcode values) - rest can be ommitted.
---
If your project is set up for it,
Github user dianacarroll commented on the pull request:
https://github.com/apache/spark/pull/1276#issuecomment-48042958
@patrickwendell Before we do that...I was doing more testing on this and
found a performance impact. The call to jrdd.id() takes much longer than I
would
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1155#issuecomment-48044062
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16347/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1303#issuecomment-48044058
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1155#issuecomment-48044059
Merged build finished.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1303#issuecomment-48044061
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16345/
---
If your project is set up for it, you can
Github user ngbinh commented on a diff in the pull request:
https://github.com/apache/spark/pull/1303#discussion_r14559944
--- Diff:
core/src/main/java/org/apache/spark/network/netty/FileServerHandler.java ---
@@ -80,4 +78,11 @@ public void exceptionCaught(ChannelHandlerContext
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1303#issuecomment-48047023
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1303#issuecomment-48047034
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1303#issuecomment-48051511
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1303#issuecomment-48051512
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16348/
---
If your
GitHub user Artjom-Metro opened a pull request:
https://github.com/apache/spark/pull/1304
SPARK-2171: Demonstrate and explain how to use Spark with Groovy
Contributes documentation that explains how one can use Spark with the
Groovy without additional wrappers. Also adds some
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1304#issuecomment-48055182
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1285#issuecomment-48061305
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1285#issuecomment-48061313
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1301#discussion_r14565428
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -67,15 +68,18 @@ object ColumnPruning extends
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/1301#discussion_r14565423
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/Optimizer.scala
---
@@ -67,15 +68,18 @@ object ColumnPruning extends
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1301#issuecomment-48062575
Another awesome addition to the optimizer! Only minor comments.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1285#issuecomment-48063203
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16349/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1285#issuecomment-48063202
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
GitHub user marmbrus opened a pull request:
https://github.com/apache/spark/pull/1305
[SPARK-2370][SQL] Decrease metadata retrieved for partitioned hive queries.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/marmbrus/spark
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1305#issuecomment-48067461
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1305#issuecomment-48067455
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1305#issuecomment-48070712
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1305#issuecomment-48070714
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16350/
---
If your
Github user YanjieGao closed the pull request at:
https://github.com/apache/spark/pull/1115
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1300#issuecomment-48075382
Merging this in master.
---
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/1300
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/1305#issuecomment-48076631
Merging this in master branch-1.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1305
---
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 ueshin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1150#discussion_r14569171
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/SparkStrategies.scala ---
@@ -274,7 +274,7 @@ private[sql] abstract class SparkStrategies
Github user kellrott commented on the pull request:
https://github.com/apache/spark/pull/1292#issuecomment-48077387
https://issues.apache.org/jira/browse/SPARK-2372
---
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 ueshin commented on the pull request:
https://github.com/apache/spark/pull/1301#issuecomment-48077448
Thank you for your comments.
Fixed and pushed.
---
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/1301#issuecomment-48077473
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1301#issuecomment-48077476
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1303#issuecomment-48077896
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1303#issuecomment-48077899
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
1 - 100 of 107 matches
Mail list logo
