Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/799#discussion_r12760581
--- Diff: bin/pyspark ---
@@ -25,6 +25,12 @@ export SPARK_HOME="$FWDIR"
SCALA_VERSION=2.10
+if [[ "$@" == *--help* ]]; then
--- End diff
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43371650
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15050/
---
If your project
Github user kanzhang commented on the pull request:
https://github.com/apache/spark/pull/760#issuecomment-43373217
@witgo I'm not sure it is the correct semantics (@mateiz ?), but based on
how we partition sequences, that is expected. We zip by partition (see below).
Btw, as
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/799#discussion_r12759324
--- Diff: python/pyspark/java_gateway.py ---
@@ -76,3 +76,30 @@ def run(self):
java_import(gateway.jvm, "scala.Tuple2")
return gateway
Github user kanzhang commented on the pull request:
https://github.com/apache/spark/pull/760#issuecomment-43378994
@witgo for sequences of the same size, we can get the same result as Scala
zip, as long as we partition them in the same way. For sequences of different
sizes (your examp
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/799#discussion_r12760554
--- Diff: bin/pyspark ---
@@ -52,13 +58,35 @@ export
PYTHONPATH=$SPARK_HOME/python/lib/py4j-0.8.1-src.zip:$PYTHONPATH
export OLD_PYTHONSTARTUP=$PYTHONSTART
GitHub user sryza opened a pull request:
https://github.com/apache/spark/pull/789
SPARK-1813. Add a utility to SparkConf that makes using Kryo really easy
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sryza/spark sandy-spark-18
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/755#issuecomment-43373145
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15052/
---
If your project
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/795#issuecomment-43263899
Hey @sryza - thanks a lot for this. We've had reports of issues with Avro
for a while and this is finally a coherent explanation of what's not working.
I'm tempted to cut
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/696
---
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/685#issuecomment-43177180
Yes, it is unmaintained but it also means that it won't change in the
future, less likely than Guava. I'm actually okay to switch to JSON by
replacing `(` and `)` by `[` an
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/769#issuecomment-43306032
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15044/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/787#issuecomment-43251370
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/788#issuecomment-43177757
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15018/
---
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/799#issuecomment-43286482
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15038/
---
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/788#issuecomment-43177449
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/787#issuecomment-43180290
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/511#issuecomment-43259522
@AndreSchumacher this is no longer merge-able. Do you mind bring it up to
date so it can be merged cleanly? Thanks.
---
If your project is set up for it, you can reply to th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/497#issuecomment-42394655
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 f
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/755#issuecomment-43373144
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/799#issuecomment-43371649
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/802#issuecomment-43372677
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/799#issuecomment-43369309
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15049/
---
If your project
Github user AndreSchumacher commented on the pull request:
https://github.com/apache/spark/pull/511#issuecomment-43359217
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/802#issuecomment-43372679
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15051/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/511#issuecomment-43368489
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15048/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/769
---
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 AndreSchumacher commented on the pull request:
https://github.com/apache/spark/pull/511#issuecomment-43370347
@rxin Thanks for the note. I just rebased 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 yo
Github user kanzhang commented on the pull request:
https://github.com/apache/spark/pull/755#issuecomment-43369939
@mateiz changed to forcing the PickleSerializer.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/511#issuecomment-43367615
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15047/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43365616
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/769#issuecomment-43364971
Thanks. I've merged this into 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 pro
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/804
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/802#issuecomment-43368762
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/802#issuecomment-43368744
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/755#issuecomment-43369709
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/799#issuecomment-43369307
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/739#issuecomment-43278462
Thanks. I've merged this into 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 pr
GitHub user ash211 opened a pull request:
https://github.com/apache/spark/pull/793
SPARK-1846 Ignore logs directory in RAT checks
https://issues.apache.org/jira/browse/SPARK-1846
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ash
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/803#issuecomment-43297858
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/804#issuecomment-43354971
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15046/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/802#issuecomment-43287880
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 jegonzal opened a pull request:
https://github.com/apache/spark/pull/720
Synthetic GraphX Benchmark
This PR accomplishes two things:
1. It introduces a Synthetic Benchmark application that generates an
arbitrarily large log-normal graph and executes either PageR
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/590#issuecomment-43188109
Submit a new Pull Request #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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/446#discussion_r12707061
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -98,13 +98,19 @@ case class And(left: Expression, right:
Github user ArcherShao commented on the pull request:
https://github.com/apache/spark/pull/740#issuecomment-43234498
PrimitiveKeyOpenHashMap has changed to GraphXPrimitiveKeyOpenHashMap, I
will send a new pull request.
---
If your project is set up for it, you can reply to this email
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/446#discussion_r12707063
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -98,13 +98,19 @@ case class And(left: Expression, right:
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/757
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/804#issuecomment-43311672
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15045/
---
If your project is set up for it, you can r
Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/659#issuecomment-43263834
Since a #652 fixed this for now, can you close this? Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. I
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/799#discussion_r12723628
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -293,8 +299,8 @@ object SparkSubmit {
}
private def addJarToCl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/792#issuecomment-43234545
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/684#issuecomment-42494009
Did some sanity checks here. On thing that's kind of weird is
`parquet-column` downgrades `commons-codec` from 1.7 to 1.5:
http://www.mvnrepository.com/artifact/c
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/702#discussion_r12460396
--- Diff: docs/mllib-optimization.md ---
@@ -128,10 +128,24 @@ is sampled, i.e. `$|S|=$ miniBatchFraction $\cdot n =
1$`, then the algorithm is
standard SG
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/798#discussion_r12721213
--- Diff: core/src/main/scala/org/apache/spark/scheduler/Task.scala ---
@@ -33,7 +33,7 @@ import org.apache.spark.util.ByteBufferInputStream
* - [[org.apache
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/800#issuecomment-43296302
btw - regarding the branch name - I don't think this was _too_ shitty of a
default. I'd actually like to have this on by default if we can get it into
working order, beca
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/700#issuecomment-42610753
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/597#issuecomment-42404743
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/649#issuecomment-42451101
@tgravescs yes the `akka` thing is intentional. Anything else with this?
I'd like to get it merged to allow us to cut another RC.
---
If your project is set up for it, y
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/769#issuecomment-43282695
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 xiliu82 opened a pull request:
https://github.com/apache/spark/pull/796
[SparkSQL] allow UDF on struct
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xiliu82/spark sqlbug
Alternatively you can review and apply these
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/511#issuecomment-43359201
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/804#issuecomment-43354970
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/511#issuecomment-43359218
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/511#issuecomment-43359714
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/636#issuecomment-42590315
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14816/
---
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/787#issuecomment-43251502
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 CodingCat commented on a diff in the pull request:
https://github.com/apache/spark/pull/636#discussion_r12471187
--- Diff:
core/src/main/scala/org/apache/spark/deploy/ApplicationDescription.scala ---
@@ -28,6 +28,7 @@ private[spark] class ApplicationDescription(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/446#issuecomment-42718956
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14856/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/719#issuecomment-42725907
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/790#issuecomment-43198077
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/685#issuecomment-42501697
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 rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/446#discussion_r12707097
--- Diff: sql/hive/src/main/scala/org/apache/spark/sql/hive/hiveUdfs.scala
---
@@ -248,17 +248,31 @@ private[hive] case class HiveGenericUdf(name: String,
childr
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/793#issuecomment-43242244
LTGM pending 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 featu
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/787#issuecomment-43251989
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/803#issuecomment-43297855
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/704
---
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 andrewor14 closed the pull request at:
https://github.com/apache/spark/pull/787
---
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 e
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/788#issuecomment-43177124
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 ueshin opened a pull request:
https://github.com/apache/spark/pull/790
[SPARK-1819] [SQL] Use AllScalaRegistrar for SparkSqlSerializer to register
serializers of ...
...Scala collections.
When I execute `orderBy` or `limit` for `SchemaRDD` including `ArrayType`
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/511#issuecomment-43359730
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/800#issuecomment-43286675
This patch is intended as a hotfix in the hopes that it can make it into
the 1.0 release. Avoiding cleaning up running applications seems like the
better solution in gene
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/800#issuecomment-43354675
Just a little miffed because it took some time to figure out why our
executors suddenly started failing with jar-not-found errors :)
I'd prefer a full solution; l
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/799#issuecomment-43284075
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 jegonzal commented on the pull request:
https://github.com/apache/spark/pull/720#issuecomment-42757213
Good point! I moved the benchmark into the examples folder. Is there a
standard format for command line args in the example applications?
---
If your project is set up
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/795
---
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 sslavic commented on the pull request:
https://github.com/apache/spark/pull/739#issuecomment-43197402
Nice, tests passed. Please consider merging, maybe even for 1.0 release.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/799#discussion_r12725362
--- Diff: bin/pyspark ---
@@ -25,6 +25,12 @@ export SPARK_HOME="$FWDIR"
SCALA_VERSION=2.10
+if [[ "$@" == *--help* ]]; then
+ echo
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/714#issuecomment-42659699
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/803#issuecomment-43300916
ah good catch! thanks. I can fix that on merge.
---
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 pr
Github user maasg commented on the pull request:
https://github.com/apache/spark/pull/756#issuecomment-43221668
Thanks for the updates! +1 (after the facts :) )
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/446
---
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 witgo commented on the pull request:
https://github.com/apache/spark/pull/760#issuecomment-43309863
In your code:
`sc.parallelize(1L to 2L,4).zip(sc.parallelize(11 to 12,4)).collect`
=>
`Array[(Long, Int)] = Array((1,11), (2,12))` Â
This is the right.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/679#issuecomment-42402699
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 mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/799#discussion_r12723563
--- Diff: core/src/main/scala/org/apache/spark/util/Utils.scala ---
@@ -1166,4 +1166,16 @@ private[spark] object Utils extends Logging {
true
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/758#issuecomment-43178500
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15017/
---
If your project
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/713#issuecomment-43298969
@pwendell
Code style issues has been fixed
---
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 mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/685#discussion_r12412535
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/linalg/Vectors.scala
---
@@ -188,3 +198,28 @@ class SparseVector(
private[mllib] override def
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/794#issuecomment-43351634
Yeah, that pretty much has the same code. If it goes in I can close this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Gi
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/597#issuecomment-42511880
Merged. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
ena
201 - 300 of 466 matches
Mail list logo
