Github user iven commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-37156504
Sorry, I was a little busy last week. I'll push new version today.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as we
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-37156438
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/108#issuecomment-37156418
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/79#issuecomment-37156437
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37156415
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/108#issuecomment-37156420
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/97#issuecomment-37156426
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 have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37156414
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/97#issuecomment-37156427
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 th
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/102#issuecomment-37156375
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13086/
---
If your p
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/106#issuecomment-37156377
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13087/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/106#issuecomment-37156376
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/102#issuecomment-37156373
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-37156364
Not sure if you saw this, @iven, but Ben put some good comments above --
would be good to fix those.
---
If your project is set up for it, you can reply to this email and h
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/108#issuecomment-37156275
Cool, looks good then.
---
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/106#issuecomment-37156227
Actually I do have one other comment, maybe we should call this
getCreationSite / creationSite so as not to confuse it with the call site of a
job. This is really the locat
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/106#discussion_r10420059
--- Diff: core/src/main/scala/org/apache/spark/SparkContext.scala ---
@@ -830,13 +830,10 @@ class SparkContext(
setLocalProperty("externalCallSite", nul
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/109#issuecomment-37156133
Yeah let's add those flags to help. I didn't realize that they weren't
shown.
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/112#issuecomment-37156103
Interesting, good catch. I might've written some of the code to get PySpark
to stop tasks early a while back.
---
If your project is set up for it, you can reply to this e
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/114
---
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 ash211 commented on the pull request:
https://github.com/apache/spark/pull/99#issuecomment-37155320
I'm used to thinking of Spark standalone clusters as having 4 different
"types" of JVMs -- 1 driver, 1 master, N workers, and M executors. Does
SPARK_DAEMON_MEMORY control
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/109#issuecomment-37154936
What if instead we added to the help docs the `-i` and `-e` flag from the
scala repl? I don't think there is any way for the user to see these now. We
should make sure th
Github user ash211 commented on the pull request:
https://github.com/apache/spark/pull/110#issuecomment-37154887
I find that new users often wonder why Spark is only using 1 core, and it's
because they expected local to use all their cores rather than defaulting to
just one. Changing
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/108#issuecomment-37154826
Hey @mateiz updated the docs.
---
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 hav
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/114#issuecomment-37154805
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
ena
Github user kellrott commented on the pull request:
https://github.com/apache/spark/pull/109#issuecomment-37154745
That would be enough for my usage. Wasn't aware of the '-i' flag, it
doesn't show up in the '--help' and wasn't mentioned when I asked about this
feature in spark-users
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/106#issuecomment-37154609
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/106#issuecomment-37154608
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 hav
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/102#issuecomment-37154606
Updated version works with sbt as well
---
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 n
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/106#issuecomment-37154596
@mateiz @aarondav This update simply removes the `generator` setters and
changes the naming as per Matei's suggestion.
---
If your project is set up for it, you can repl
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/114#issuecomment-37154497
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/102#issuecomment-37154500
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/102#issuecomment-37154499
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/112#issuecomment-37154483
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13085/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/112#issuecomment-37154481
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/113#issuecomment-37154480
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/113#issuecomment-37154482
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13084/
---
If your p
GitHub user CrazyJvm opened a pull request:
https://github.com/apache/spark/pull/114
maintain arbitrary state data for each key
RT
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/CrazyJvm/spark patch-1
Alternatively you can revie
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37152830
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/112#issuecomment-37152832
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/112#issuecomment-37152831
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/113#issuecomment-37152829
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 hav
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/113
Upgrade Jetty to 9.1.3.v20140225.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rxin/spark jetty9
Alternatively you can review and apply these ch
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/112#issuecomment-37152085
/cc @joshrosen
---
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 pwendell opened a pull request:
https://github.com/apache/spark/pull/112
SPARK-1019: pyspark RDD take() throws an NPE
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pwendell/spark pyspark-take
Alternatively you can
Hi!
while compiling a board report, I have noticed
that the following podlings still haven't completed
the graduation steps wrt. updating the Incubator
tracking and removing themselves. Please make
sure to follow instructions over here:
http://incubator.apache.org/guides/graduation.html#life-af
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/101#issuecomment-37150695
anyone would like to review 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 project does no
Github user CodingCat commented on the pull request:
https://github.com/apache/spark/pull/35#issuecomment-37150704
ping
---
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 CodingCat commented on the pull request:
https://github.com/apache/spark/pull/12#issuecomment-37150712
ping
---
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 pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/108#discussion_r10417447
--- Diff: docs/monitoring.md ---
@@ -48,11 +48,22 @@ Each instance can report to zero or more _sinks_. Sinks
are contained in the
* `ConsoleSink`:
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/106#discussion_r10417424
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1031,8 +1026,10 @@ abstract class RDD[T: ClassTag](
private var storageLevel:
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/106#discussion_r10417318
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -1031,8 +1026,10 @@ abstract class RDD[T: ClassTag](
private var storageLevel: S
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/106#issuecomment-37147113
I'd say just remove them -- this is a pretty small feature and easy to work
around if anyone used it.
---
If your project is set up for it, you can reply to this email and
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/109#issuecomment-37147073
You can actually already use the `-i` argument on `spark-shell` (similar to
on `scala`) to load a script at the beginning. Is that enough? We don't want to
diverge too much
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/108#discussion_r10417262
--- Diff: docs/monitoring.md ---
@@ -48,11 +48,22 @@ Each instance can report to zero or more _sinks_. Sinks
are contained in the
* `ConsoleSink`: Lo
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/100
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/108#issuecomment-37137320
@aarondav the spark-ec2 scripts set up a ganglia cluster separately... they
actually don't use the `GangliaSink` in Spark at present. If change spark ec2
to use that then
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/108#issuecomment-37136294
Will this require the spark-ec2 scripts to pull in this dependency as well?
---
If your project is set up for it, you can reply to this email and have your
reply appear o
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37136247
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/100#issuecomment-37136248
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13083/
---
If your project
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/106#issuecomment-37136132
As per our offline discussion let's either just remove the existing
function calls (which is okay since this is a 1.0 release) or continue to
support them with deprecatio
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/111
---
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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/98
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/108#issuecomment-37135373
@mateiz if you could take a glance at this that would be great. This has to
get merged into 0.9.1 so I want to make sure a few people look at it.
---
If your project is
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/111
Fix markup errors introduced in #33 (SPARK-1189)
These were causing errors on the configuration page.
You can merge this pull request into a Git repository by running:
$ git pull https://github
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/98#issuecomment-37134421
@guojc actually on second though I can just add a quick doc.
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/106#discussion_r10414992
--- Diff: core/src/main/scala/org/apache/spark/api/java/JavaRDD.scala ---
@@ -135,7 +135,11 @@ class JavaRDD[T](val rdd: RDD[T])(implicit val
classTag: ClassT
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37134276
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 hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37134277
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 t
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/106#issuecomment-37133978
Just had a couple questions essentially related to our deprecation policy.
Change looks good to me otherwise. Thanks for the cleanup!
---
If your project is set up for i
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/99
---
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 aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/106#discussion_r10414915
--- Diff: core/src/main/scala/org/apache/spark/api/java/JavaRDD.scala ---
@@ -135,7 +135,11 @@ class JavaRDD[T](val rdd: RDD[T])(implicit val
classTag: ClassT
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/106#discussion_r10414905
--- Diff: core/src/main/scala/org/apache/spark/api/java/JavaRDD.scala ---
@@ -135,7 +135,11 @@ class JavaRDD[T](val rdd: RDD[T])(implicit val
classTag: ClassT
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/98#issuecomment-37133850
@guojc I think this looks good. Do you mind adding an entry for this in
`docs/configuration.md`?
---
If your project is set up for it, you can reply to this email and hav
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37133631
Okay I'm going to merge this into master. Did some local testing and things
seem to be working.
---
If your project is set up for it, you can reply to this email and hav
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/110#issuecomment-37121987
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
76 matches
Mail list logo
