Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/933#issuecomment-44766970
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/933#issuecomment-44766971
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15325/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/933#issuecomment-44766468
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/933#issuecomment-44766465
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 ha
GitHub user ankurdave opened a pull request:
https://github.com/apache/spark/pull/933
Add landmark-based Shortest Path algorithm to graphx.lib
This is a modified version of apache/spark#10.
You can merge this pull request into a Git repository by running:
$ git pull https://git
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/933#issuecomment-44766447
@rxin
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/932
---
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 enabl
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/932#issuecomment-44766071
Thanks. I've merged 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 proje
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/932#issuecomment-44765993
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 proj
GitHub user yadid opened a pull request:
https://github.com/apache/spark/pull/932
updated java code blocks in spark SQL guide such that ctx will refer to ...
...a JavaSparkContext and sqlCtx will refer to a JavaSQLContext
You can merge this pull request into a Git repository by runn
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/866#issuecomment-44761085
Thanks Uri. Merged this into branch-1.0 as well as 0.9.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If y
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/866
---
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 enabl
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/796#issuecomment-44760575
Thanks for working on this!
Looks like adding the extra function is breaking the `show_functions` test.
Maybe cleanup by deleting that new UDF at the end of your
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/786
---
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 enabl
Github user cfregly commented on the pull request:
https://github.com/apache/spark/pull/223#issuecomment-44760308
update: i discusses this with parviz recently - and we agreed that i would
take this over. new PR to come shortly. here's the jira ticket:
https://issues.apache.org/ji
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/796#issuecomment-44758567
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/796#issuecomment-44758568
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15324/
---
If your project is set up for it, you can r
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/897#discussion_r13263116
--- Diff: core/src/main/scala/org/apache/spark/api/java/JavaPairRDD.scala
---
@@ -672,38 +672,102 @@ class JavaPairRDD[K, V](val rdd: RDD[(K, V)])
/*
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/781#discussion_r13263105
--- Diff: repl/src/test/scala/org/apache/spark/repl/ReplSuite.scala ---
@@ -44,15 +44,19 @@ class ReplSuite extends FunSuite {
}
}
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/922
---
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 enabl
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/922#issuecomment-44758293
Thanks. I merged 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
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/781#discussion_r13263078
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/SparkDeploySchedulerBackend.scala
---
@@ -44,7 +44,8 @@ private[spark] class SparkDeploySche
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/914
---
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 enabl
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/914#issuecomment-44757533
Ok merging this in master & branch-1.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 projec
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/913
---
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 enabl
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/913#issuecomment-44757474
Merging this into master & branch-1.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 projec
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/801
---
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 enabl
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/801#issuecomment-44757201
Merged into master and branch-1.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 project
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/801#issuecomment-44757169
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
enabled an
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/796#issuecomment-44756643
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/796#issuecomment-44756639
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 ha
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/796#issuecomment-44756553
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 this featur
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/837#issuecomment-44756501
Can you add "[SPARK-1495][SQL]" to the PR title?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your p
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/837#discussion_r13262730
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins.scala ---
@@ -144,6 +144,150 @@ case class HashJoin(
* :: DeveloperApi ::
*
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/837#issuecomment-44756469
This is getting closer. 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 GitHub as well. If your
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/837#discussion_r13262710
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins.scala ---
@@ -144,6 +144,150 @@ case class HashJoin(
* :: DeveloperApi ::
*
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/837#discussion_r13262704
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins.scala ---
@@ -144,6 +144,150 @@ case class HashJoin(
* :: DeveloperApi ::
*
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/786#issuecomment-44756289
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15323/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/786#issuecomment-44756288
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. If
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/837#discussion_r13262687
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins.scala ---
@@ -144,6 +144,150 @@ case class HashJoin(
* :: DeveloperApi ::
*
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/837#discussion_r13262640
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins.scala ---
@@ -144,6 +144,150 @@ case class HashJoin(
* :: DeveloperApi ::
---
Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/837#discussion_r13262607
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins.scala ---
@@ -144,6 +144,150 @@ case class HashJoin(
* :: DeveloperApi ::
*
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/912#issuecomment-44755843
Sure. I have closed it.
---
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 fe
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/902#issuecomment-44755822
Thanks! merged into master and 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 no
Github user yhuai closed the pull request at:
https://github.com/apache/spark/pull/912
---
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 enable
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/902
---
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 enabl
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/909#issuecomment-44755719
We should probably have a test for this... maybe something like:
```scala
createQueryTest("nulls",
"""
|CREATE TABLE nullVals AS SELECT "nu
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44755561
So I've actually been assuming that users running older versions of Mesos
just change `mesos.version` in the build and package Spark, so in my head I've
sort of coupled "
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44755392
Yes looks like it was introduced in 0.17.0:
https://github.com/apache/mesos/commit/b609c851493c81c6ba8dfe51cf102400c05c2d0c
I see, I thought the intent was to requi
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/912#issuecomment-44755346
@yhuai mind closing this? Our "auto close" thing doesn't work for back
ports like this.
---
If your project is set up for it, you can reply to this email and have your
r
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/914#discussion_r13262479
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -381,16 +381,19 @@ private[spark] class SparkSubmitArguments(args:
Seq[
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/786#issuecomment-44755221
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/786#issuecomment-44755219
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 ha
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/786#issuecomment-44755096
Jenkins, test this please. Thanks for this @witgo - this is good clean-up.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44755003
Hey Sean - do you know if this will break Spark for Mesos 15/16/17? When
did the introduce the newer API? We should definitely update this... I'm a bit
concerned about bu
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/914#discussion_r13262410
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -381,16 +381,19 @@ private[spark] class SparkSubmitArguments(args:
Se
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44753736
I'm just copying-and-pasting to get something similar running externally.
Maybe it's a little surprising that the example code doesn't work that way --
being in a `main()`
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44753603
Hey Sean, how are you running the examples. Are you using the `run-example`
script? That script should set the master to `local[*]` if the user hasn't
specified it, which
Github user nevillelyh commented on the pull request:
https://github.com/apache/spark/pull/925#issuecomment-44750919
Sure that would also work. I made a PR to chill as well.
https://github.com/twitter/chill/pull/185
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-44749478
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-44749479
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15322/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-44749436
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/931#issuecomment-44749434
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 ha
GitHub user xiajunluan opened a pull request:
https://github.com/apache/spark/pull/931
Fix JIRA-983 and support exteranl sort for sortByKey
Change class ExternalAppendOnlyMap and make it support customized
comparator function(not only sorted by hashCode).
You can merge this pull re
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44747313
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44747315
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15321/
---
If your project is set up for it, you can r
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44746537
I pushed again, with `setIfMissing`. Is it better in the `SparkConf`
constructor? or I am off base here?
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44746504
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44746502
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 ha
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/792#issuecomment-44746294
Thanks, I meant to do this a while ago but never got around to it.
The code duplication is unfortunate, though. Why not just have
toEdgePartition take an optiona
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/901#issuecomment-44746122
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15320/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/901#issuecomment-44746121
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/901#issuecomment-44746090
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/901#issuecomment-44746088
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 ha
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/901#issuecomment-44746040
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
ena
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/901#issuecomment-44745827
Unlike Python (but like Java), Scala doesn't use asInstanceOf for arbitrary
type conversions. In this case, it won't work to do `"123".asInstanceOf[Int]`,
because Scala
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/930#issuecomment-44745616
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 proj
GitHub user pankajarora12 opened a pull request:
https://github.com/apache/spark/pull/930
[SPARK-1979] Added Error Handling if user passes application params with...
Added error message to user when used --arg for passing application
parameters.
You can merge this pull request into
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44745344
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44745345
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15319/
---
If your project
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44744710
Yeah I think it's essential to not prevent `-Dspark.master=...` from
working, oops. I think it may be useful to have this work if one
copies-and-pastes too, as I just did.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44744576
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 ha
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44744577
Oops, yes, coming up now.
---
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/920#issuecomment-44744579
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 have
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/914#discussion_r13260477
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -381,16 +381,19 @@ private[spark] class SparkSubmitArguments(args:
Seq[
Github user MLnick commented on the pull request:
https://github.com/apache/spark/pull/455#issuecomment-44743612
@mateiz I noticed that the docs for Python programming guid have been
merged into the overall Programming guide.
Where do you think the best place is to put the bi
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/929#issuecomment-44742948
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/929#issuecomment-44742949
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15318/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/929#issuecomment-44742668
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15317/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/929#issuecomment-44742667
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/894#issuecomment-44742298
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15316/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/894#issuecomment-44742297
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. If
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/897#issuecomment-44742270
@pwendell Jenkins failed due to binary compatibility for
SerializableHyperLogLog, which is no longer needed ...
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/929#issuecomment-44742189
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 ha
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/929#issuecomment-44742193
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/897#issuecomment-44742112
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15315/
---
If your project is set up for it, you can r
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/897#issuecomment-44742111
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 have
Github user witgo closed the pull request at:
https://github.com/apache/spark/pull/828
---
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 enable
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/828#issuecomment-44742037
This solution is not perfect. temporarily close this. The new #929 .
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/929#issuecomment-44742011
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 have
1 - 100 of 116 matches
Mail list logo
