Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/701#issuecomment-42729688
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14866/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/730#issuecomment-42763089
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 witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/646#discussion_r12507598
--- Diff: conf/spark-env.sh.template ---
@@ -38,6 +38,7 @@
# - SPARK_WORKER_INSTANCES, to set the number of worker processes per node
# -
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/730
SPARK-1652: Set driver memory correctly in spark-submit.
The previous check didn't account for the fact that the default
deploy mode is client unless otherwise specified. Also, this
sets the
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/646#discussion_r12507600
--- Diff: conf/spark-env.sh.template ---
@@ -38,6 +38,7 @@
# - SPARK_WORKER_INSTANCES, to set the number of worker processes per node
# -
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/730#issuecomment-42763096
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/730#issuecomment-42763144
This was reported by @witgo.
---
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 closed the pull request at:
https://github.com/apache/spark/pull/646
---
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/720#issuecomment-42756947
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14876/
---
If your project is set up for it, you can
GitHub user pjopensource opened a pull request:
https://github.com/apache/spark/pull/693
SPARK-1759
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pjopensource/spark branch-0.9
Alternatively you can review and apply these
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/685#issuecomment-42501713
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/582#issuecomment-42623759
Thanks, merged.
---
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 witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/646#discussion_r12507619
--- Diff: conf/spark-env.sh.template ---
@@ -38,6 +38,7 @@
# - SPARK_WORKER_INSTANCES, to set the number of worker processes per node
# -
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/729#issuecomment-42763487
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/729#issuecomment-42763488
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14883/
---
If your project
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/728#issuecomment-42763506
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 aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/639#discussion_r12490657
--- Diff:
core/src/main/scala/org/apache/spark/deploy/master/MasterMessages.scala ---
@@ -39,4 +39,6 @@ private[master] object MasterMessages {
case
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/728#issuecomment-42763556
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/730#issuecomment-42763555
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14884/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/728#issuecomment-42763553
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/685#discussion_r12503350
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/util/NumericParser.scala ---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/685#discussion_r12502576
--- Diff:
mllib/src/main/scala/org/apache/spark/mllib/util/NumericParser.scala ---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the Apache Software Foundation
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/730#issuecomment-42763554
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/715#issuecomment-42763346
/cc @scrapcodes who worked on the IndestructableActorSystem
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user patrickotoole commented on a diff in the pull request:
https://github.com/apache/spark/pull/537#discussion_r12507593
--- Diff:
streaming/src/main/scala/org/apache/spark/streaming/StreamingContext.scala ---
@@ -327,18 +327,18 @@ class StreamingContext private[streaming]
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/646#issuecomment-42763279
A better solution [PR 730](https://github.com/apache/spark/pull/730)
---
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/728#issuecomment-42764076
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14885/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/728#issuecomment-42764075
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 lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/636#discussion_r12507640
--- Diff:
core/src/main/scala/org/apache/spark/deploy/ApplicationDescription.scala ---
@@ -28,6 +28,7 @@ private[spark] class ApplicationDescription(
GitHub user ajtulloch opened a pull request:
https://github.com/apache/spark/pull/725
SPARK-1791 - SVM implementation does not use threshold parameter
Summary:
https://issues.apache.org/jira/browse/SPARK-1791
Simple fix, and backward compatible, since
- anyone
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/710
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/525
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/684#issuecomment-42750659
Thanks for taking a look michael - I merged this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/701#discussion_r12505284
--- Diff: docs/spark-standalone.md ---
@@ -150,20 +162,30 @@ You can also pass an option `--cores numCores` to
control the number of cores
Spark
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/688
The org.datanucleus:* should not be packaged into spark-assembly-*.jar
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark SPARK-1644
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/649#issuecomment-42427401
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 markhamstra commented on the pull request:
https://github.com/apache/spark/pull/706#issuecomment-42697568
https://issues.apache.org/jira/browse/SPARK-1776
---
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/702#discussion_r12460491
--- Diff: docs/mllib-optimization.md ---
@@ -163,3 +177,100 @@ each iteration, to compute the gradient direction.
Available algorithms for gradient
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/701#issuecomment-42713025
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 srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/723#discussion_r12507895
--- Diff: core/src/test/scala/org/apache/spark/LocalSparkContext.scala ---
@@ -17,8 +17,7 @@
package org.apache.spark
-import
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/685#discussion_r12502581
--- Diff: python/pyspark/mllib/linalg.py ---
@@ -234,6 +233,45 @@ def dense(elements):
return array(elements, dtype=float64)
+
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/715#issuecomment-42716337
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14854/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/552#issuecomment-42520748
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/723
---
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/722#issuecomment-42738393
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/720#issuecomment-42756921
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 a diff in the pull request:
https://github.com/apache/spark/pull/704#discussion_r12462266
--- Diff: bin/run-example ---
@@ -49,46 +31,31 @@ fi
if [[ -z $SPARK_EXAMPLES_JAR ]]; then
echo Failed to find Spark examples assembly in
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/603#discussion_r12388303
--- Diff:
core/src/main/scala/org/apache/spark/api/python/PythonWorkerFactory.scala ---
@@ -208,6 +170,19 @@ private[spark] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/651#issuecomment-42608067
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/636#issuecomment-42504239
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 techaddict commented on a diff in the pull request:
https://github.com/apache/spark/pull/597#discussion_r12389144
--- Diff:
examples/src/main/scala/org/apache/spark/examples/mllib/MovieLensALS.scala ---
@@ -121,11 +157,14 @@ object MovieLensALS {
}
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/680#issuecomment-42485074
Thanks. Merged.
---
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 jaceklaskowski commented on a diff in the pull request:
https://github.com/apache/spark/pull/706#discussion_r12508408
--- Diff: project/SparkBuild.scala ---
@@ -297,7 +273,7 @@ object SparkBuild extends Build {
val chillVersion = 0.3.6
val
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/706#issuecomment-42768086
This is what Patrick was trying to say
https://issues.apache.org/jira/browse/SPARK-1776. So while we have this on our
mind, even if we merge this patch it has to
Github user CodingCat commented on a diff in the pull request:
https://github.com/apache/spark/pull/636#discussion_r12508764
--- Diff:
core/src/main/scala/org/apache/spark/deploy/ApplicationDescription.scala ---
@@ -28,6 +28,7 @@ private[spark] class ApplicationDescription(
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/644#issuecomment-42752706
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/603#issuecomment-42469138
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14780/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/679
---
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 commented on the pull request:
https://github.com/apache/spark/pull/686#issuecomment-42494200
@CodingCat @kayousterhout @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
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/597#discussion_r12407485
--- Diff:
examples/src/main/scala/org/apache/spark/examples/mllib/MovieLensALS.scala ---
@@ -121,11 +157,23 @@ object MovieLensALS {
}
/**
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/497#issuecomment-42489547
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 sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/701#discussion_r12456854
--- Diff: docs/running-on-yarn.md ---
@@ -68,11 +69,12 @@ In yarn-cluster mode, the driver runs on a different
machine than the client, so
$
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/661
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/539#issuecomment-42512812
I dug through the code a bunch. For those following this PR, here's a quick
summary. Looks like the way we set Spark app name on YARN is actually quite
convoluted
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/497#issuecomment-42483855
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/686#issuecomment-42494319
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14790/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/704#issuecomment-42633729
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 mridulm commented on the pull request:
https://github.com/apache/spark/pull/514#issuecomment-42525085
Closing this assuming it has been resolved through other PR's. Please let
me know in case this is not the case.
---
If your project is set up for it, you can reply to
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/651#discussion_r12450552
--- Diff: sbin/spark-executor ---
@@ -19,5 +19,10 @@
FWDIR=$(cd `dirname $0`/..; pwd)
+sbin=`dirname $0`
+sbin=`cd $sbin; pwd`
+
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/446#issuecomment-42718954
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 your
Github user scwf commented on the pull request:
https://github.com/apache/spark/pull/714#issuecomment-42770141
Hi @pwendell, thanks. I didn't notice validateSettings in SparkConf and
it's good to validate this in it.
---
If your project is set up for it, you can reply to this email
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/332#issuecomment-42771828
@pwendell @marmbrus @rxin
typesafehub/scala-logging#4 has been solved by typesafehub/scala-logging#15
The PR should be able to merge into master master
---
If
Github user CodingCat closed the pull request at:
https://github.com/apache/spark/pull/636
---
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 lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/636#discussion_r12509207
--- Diff:
core/src/main/scala/org/apache/spark/deploy/ApplicationDescription.scala ---
@@ -28,6 +28,7 @@ private[spark] class ApplicationDescription(
GitHub user srowen opened a pull request:
https://github.com/apache/spark/pull/732
SPARK-1798. Tests should clean up temp files
Three issues related to temp files that tests generate â these should be
touched up for hygiene but are not urgent.
Modules have a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/731#issuecomment-42772900
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 a diff in the pull request:
https://github.com/apache/spark/pull/720#discussion_r12502303
--- Diff:
graphx/src/main/scala/org/apache/spark/graphx/lib/SynthBenchmark.scala ---
@@ -0,0 +1,136 @@
+package org.apache.spark.graphx.lib
+
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/731#issuecomment-42773948
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/731#issuecomment-42773949
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14886/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/732#issuecomment-42773573
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/731#issuecomment-42772897
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 markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/706#discussion_r12509377
--- Diff: project/SparkBuild.scala ---
@@ -297,7 +273,7 @@ object SparkBuild extends Build {
val chillVersion = 0.3.6
val
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/702#discussion_r12460376
--- Diff: docs/mllib-optimization.md ---
@@ -163,3 +177,100 @@ each iteration, to compute the gradient direction.
Available algorithms for gradient
Github user markhamstra commented on a diff in the pull request:
https://github.com/apache/spark/pull/706#discussion_r12489193
--- Diff: project/SparkBuild.scala ---
@@ -16,17 +16,18 @@
*/
import sbt._
-import sbt.Classpaths.publishTask
-import sbt.Keys._
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42673811
Although there's now a 'fix' in, it is only going to do automatically what
you are doing by hand.
My hunch is that perhaps the script, or env variable, already contains
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/647#issuecomment-42465768
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/699#issuecomment-42630934
I've merged 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. If your project does not have
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/702#discussion_r12460451
--- Diff: docs/mllib-optimization.md ---
@@ -163,3 +177,100 @@ each iteration, to compute the gradient direction.
Available algorithms for gradient
Github user ankurdave commented on a diff in the pull request:
https://github.com/apache/spark/pull/497#discussion_r12456034
--- Diff:
graphx/src/main/scala/org/apache/spark/graphx/impl/ReplicatedVertexView.scala
---
@@ -21,192 +21,102 @@ import scala.reflect.{classTag, ClassTag}
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/649#issuecomment-42423123
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 darose commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42635850
I tried downloading the latest from the master branch of both spark and
shark, and built and ran them (in the hopes of getting past that class
incompatible issue) but no
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/687
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/710#issuecomment-42634045
We may not always want to automatically add the jar to `spark.jar`. I will
spend some time looking into cases in which we want to skip this (which likely
involves
Github user tgravescs commented on the pull request:
https://github.com/apache/spark/pull/701#issuecomment-42715097
thanks for the update, the changes look good to me.
I did notice one other thing in the yarn docs and that is that we don't say
what parameters spark-shell
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/732#issuecomment-42773567
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/732#issuecomment-42774629
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/732#issuecomment-42774630
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14887/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/731#issuecomment-42774784
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/733#issuecomment-42775785
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 CodingCat opened a pull request:
https://github.com/apache/spark/pull/731
SPARK-1706: Allow multiple executors per worker in Standalone mode
resubmit of SPARK-1706 for a totally different algorithm
You can merge this pull request into a Git repository by running:
$
1 - 100 of 236 matches
Mail list logo
