Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/597#issuecomment-42458899
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/703
---
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 kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/686#discussion_r12408454
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1148,7 +1154,11 @@ private[scheduler] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/685#issuecomment-42503177
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14795/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/701#issuecomment-42728908
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-42508628
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14800/
---
If your project
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/710#issuecomment-42692803
Yes, for yarn-cluster, we're not replacing the `app.jar`, so there should
be no backward compatibility issues. The only question is whether adding it to
`spark.jar`
GitHub user aarondav opened a pull request:
https://github.com/apache/spark/pull/715
[RFC] SPARK-1772 Stop catching Throwable, let Executors die
The main issue this patch fixes is
[SPARK-1772](https://issues.apache.org/jira/browse/SPARK-1772), in which
Executors may not die when
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/679#issuecomment-42481869
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/552#issuecomment-42411313
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 mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/597#discussion_r12407659
--- Diff:
examples/src/main/scala/org/apache/spark/examples/mllib/MovieLensALS.scala ---
@@ -99,7 +123,18 @@ object MovieLensALS {
val splits =
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/673#issuecomment-42389414
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14755/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/685#issuecomment-42503175
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/636#issuecomment-42663644
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14847/
---
If your project is set up for it, you can
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/704#issuecomment-42633622
@andrewor14 great - thanks for the feedback!
---
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 ash211 commented on the pull request:
https://github.com/apache/spark/pull/690#issuecomment-42517256
/cc: @marmbrus
---
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 scwf opened a pull request:
https://github.com/apache/spark/pull/695
delete method never used
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/scwf/spark deletenousemethod
Alternatively you can review and apply these
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/675#issuecomment-42456349
Would you mind removing the Try in ShuffleMapTask which I should've removed
in #640 but failed to actually push? 3
---
If your project is set up for it, you can reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/708#issuecomment-42631533
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14834/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/643#issuecomment-42636075
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/687#issuecomment-42511999
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/552#issuecomment-42402364
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14765/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/636#issuecomment-42597847
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/656#issuecomment-42604234
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 advancedxy commented on the pull request:
https://github.com/apache/spark/pull/546#issuecomment-42525924
Sorry for being late for this conversation. I am busy with my own project.
First, I agree with @srowen. SPARK-1527 was discovered when there were
untracked
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/546#issuecomment-42484142
@pwendell @nsuthar
First, note SPARK-1527 (https://issues.apache.org/jira/browse/SPARK-1527)
and its PR (https://github.com/apache/spark/pull/436).
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/716#issuecomment-42717963
Merged into 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 project does
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/713
[WIP] update scalatest to version 2.1.5
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark scalatest
Alternatively you can review and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/675#issuecomment-42402715
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 witgo commented on the pull request:
https://github.com/apache/spark/pull/677#issuecomment-42442064
@pwendell
How about [this
solution](https://github.com/witgo/spark/compare/SPARK-1712_new)?
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/700#issuecomment-42618664
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/719#issuecomment-42725861
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/636#issuecomment-42633957
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14837/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/497#issuecomment-42484874
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14783/
---
If your project is set up for it, you can
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42453279
@manishamde Could you add docs for `numGroups` and `groupIndex` to
`findBestSplitsPerGroup`?
---
If your project is set up for it, you can reply to this email and have
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/679#issuecomment-42481268
I thought we were already doing this. Good catch!
@pwendell or @rxin, please merge.
---
If your project is set up for it, you can reply to this email and have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/475
---
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/702#issuecomment-42727304
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14860/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/701#issuecomment-42617890
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 dbtsai opened a pull request:
https://github.com/apache/spark/pull/703
MLlib documentation fix
Fixed the documentation for that `loadLibSVMData` is changed to
`loadLibSVMFile`.
You can merge this pull request into a Git repository by running:
$ git pull
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/701#issuecomment-42716087
AFAIK the latest spark-shell passes its arguments directly to spark-submit,
so in that sense spark-shell inherits whatever parameters spark-submit takes
in.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/695#issuecomment-42565337
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/552#issuecomment-42405191
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 this
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/704
SPARK-1565 (Addendum): Replace `run-example` with `spark-submit`.
Gives a nicely formatted message to the user when `run-example` is run to
tell them to use `spark-submit`.
You can merge this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/539
---
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/636#issuecomment-42506263
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/597#issuecomment-42463271
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14777/
---
If your project
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/661#discussion_r12389263
--- Diff:
mllib/src/test/scala/org/apache/spark/mllib/linalg/BreezeVectorConversionSuite.scala
---
@@ -55,4 +55,16 @@ class BreezeVectorConversionSuite
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/712
fix building spark with maven documentation
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark building-with-maven
Alternatively you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/700#issuecomment-42617519
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14825/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/639#issuecomment-42726702
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 mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/636#discussion_r12380305
--- Diff:
core/src/main/scala/org/apache/spark/deploy/ApplicationDescription.scala ---
@@ -20,7 +20,7 @@ package org.apache.spark.deploy
private[spark]
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/689#issuecomment-42516536
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/649#issuecomment-42427404
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14773/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/696#issuecomment-42587461
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/636#issuecomment-42663642
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 kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/686#discussion_r12408229
--- Diff: core/src/main/scala/org/apache/spark/scheduler/DAGScheduler.scala
---
@@ -1148,7 +1154,11 @@ private[scheduler] class
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/706#issuecomment-42700893
As to the changes I proposed in the PR, I think that however the future
steps with sbt-pom-reader they're easily applicable to the build. They (are
supposed to)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/497#issuecomment-42484873
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/673
---
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/597#issuecomment-42502537
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14793/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/700#issuecomment-42617517
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/710#issuecomment-42634085
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 ankurdave commented on a diff in the pull request:
https://github.com/apache/spark/pull/497#discussion_r12454050
--- Diff:
graphx/src/main/scala/org/apache/spark/graphx/impl/EdgePartition.scala ---
@@ -100,7 +147,23 @@ class EdgePartition[@specialized(Char, Int,
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/597#issuecomment-42456355
@techaddict Thanks for running the experiments! The results definitely look
better than `3.x` if we compute RMSE directly for implicit ALS. In the
future, we may
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/708#issuecomment-42631531
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/656#issuecomment-42608170
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/689#issuecomment-42520521
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/643#issuecomment-42691596
@dongwang218 There are two issues with stochastic updates:
1. It depends on the ordering of the training examples. Users are not
instructed to randomize the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/685#issuecomment-42489269
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 nishkamravi2 opened a pull request:
https://github.com/apache/spark/pull/691
Fix for SPARK-1758: failing test org.apache.spark.JavaAPISuite.wholeText...
...Files
The prefix file: is missing in the string inserted as key in HashMap.
You can merge this pull
Github user manishamde commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42494975
Sure!
On Wed, May 7, 2014 at 4:02 PM, Patrick Wendell
notificati...@github.comwrote:
@manishamde https://github.com/manishamde this needs to be
GitHub user willb opened a pull request:
https://github.com/apache/spark/pull/717
SPARK-571: forbid return statements in cleaned closures
This patch checks top-level closure arguments to `ClosureCleaner.clean` for
`return` statements and raises an exception if it finds any. This
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/715#issuecomment-42712542
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/636#issuecomment-42672008
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14848/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/636#issuecomment-42660437
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14846/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/685#issuecomment-42623389
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 andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/704#discussion_r12464498
--- Diff: bin/run-example ---
@@ -49,46 +31,29 @@ fi
if [[ -z $SPARK_EXAMPLES_JAR ]]; then
echo Failed to find Spark examples assembly in
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/643#issuecomment-42636082
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/640
---
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/661#issuecomment-42392717
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/716#issuecomment-42718957
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14857/
---
If your project
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/639#issuecomment-42726685
@aarondav thanks for the comments, just addressed 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
Github user mengxr commented on a diff in the pull request:
https://github.com/apache/spark/pull/597#discussion_r12388719
--- Diff:
examples/src/main/scala/org/apache/spark/examples/mllib/MovieLensALS.scala ---
@@ -99,7 +123,18 @@ object MovieLensALS {
val splits =
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/689#issuecomment-42515916
Thanks for doing this! I think we are also missing ! (not).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/546#issuecomment-42454571
@mridulm @srowen sorry not totally following this one. Is there an
immediate isolated bug here, or is this a broader issue that we need to add
consistency across the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/678#issuecomment-42403313
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14764/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/636#issuecomment-42512582
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14801/
---
If your project is set up for it, you can
Github user ankurdave commented on a diff in the pull request:
https://github.com/apache/spark/pull/497#discussion_r12453694
--- Diff: graphx/src/main/scala/org/apache/spark/graphx/VertexRDD.scala ---
@@ -276,14 +286,31 @@ class VertexRDD[@specialized VD: ClassTag](
*/
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/709#issuecomment-42706715
Looks good! You can see evidence that this fixes a bug by changing n in
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/636#issuecomment-42505971
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 CodingCat commented on a diff in the pull request:
https://github.com/apache/spark/pull/636#discussion_r12473704
--- 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/675#issuecomment-42454087
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/706#issuecomment-42628031
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/701#issuecomment-42718819
I see where the programming guide mentions a couple of options but I think
it would be good to explicitly say it since people moving from 0.9 to 1.0 might
not know
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/588#issuecomment-42494227
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/649
---
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/710#issuecomment-42635624
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14842/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/639#issuecomment-42727778
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14865/
---
If your project
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/640#discussion_r12389302
--- Diff: core/src/main/scala/org/apache/spark/api/python/PythonRDD.scala
---
@@ -210,10 +126,15 @@ private[spark] class PythonRDD[T: ClassTag](
1 - 100 of 215 matches
Mail list logo
