Github user sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/86#discussion_r10397696
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -0,0 +1,160 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) unde
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-37064297
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13053/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/99#issuecomment-37064300
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/96#issuecomment-37064311
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13052/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/99#issuecomment-37064301
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13054/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-37064296
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 fea
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/96#issuecomment-37064310
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 t
Github user sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/86#discussion_r10399046
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -0,0 +1,160 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) unde
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/90#issuecomment-37070466
@sryza I looked into this a bit more. I think there is a simpler solution
where we just use the shaded version of asm that kryo (conveniently) publishes
in their jars. I'm
Github user ahirreddy commented on a diff in the pull request:
https://github.com/apache/spark/pull/30#discussion_r10403945
--- Diff: python/Makefile ---
@@ -0,0 +1,7 @@
+assembly: clean
+ python setup.py build --build-lib build/lib
+ unzip lib/py4j*.zip -d build/lib
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37079388
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-37079389
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 pwendell opened a pull request:
https://github.com/apache/spark/pull/100
SPARK-782 Clean up for ASM dependency.
This makes two changes.
1) Spark uses the shaded version of asm that is (conveniently) published
with Kryo.
2) Existing exclude rules around
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37079425
Come to think of it, we may want to stop excluding asm now since we don't
directly use it anymore (therefore there can be no conflicts w/ Spark).
---
If your project is
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/86#discussion_r10405655
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkSubmit.scala ---
@@ -0,0 +1,160 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) u
GitHub user CodingCat opened a pull request:
https://github.com/apache/spark/pull/101
SPARK-1128: set hadoop task properties when constructing HadoopRDD
The task properties are set when constructing HadoopRDD in current
implementation, this may limit the implementation based on
import java.io.IOException;
import java.io.Serializable;
import java.io.UnsupportedEncodingException;
import java.nio.ByteBuffer;
import java.util.Collections;
import java.util.List;
import java.util.Map;
import java.util.Set;
import java.util.TreeMap;
import java.util.regex.Matcher;
import org.ap
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37082364
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-37082365
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13055/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/101#issuecomment-37082402
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/101#issuecomment-37082403
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 hsaputra commented on a diff in the pull request:
https://github.com/apache/spark/pull/86#discussion_r10406142
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -0,0 +1,153 @@
+/*
+ * Licensed to the Apache Software Foundati
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37082518
This patch looks good to me. ASM still needs to be excluded from chill,
right?
---
If your project is set up for it, you can reply to this email and have your
reply appear
if you shade asm 4.0 then wont you be forced to build your own version of
everything that uses asm 4.0?
currently we exclude asm 3.x. curious to know what is wrong with that? is
it breaking functionality somewhere else?
On Fri, Mar 7, 2014 at 4:37 PM, pwendell wrote:
> Github user pwendell
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37084570
Will this also work on Java 8?
---
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/92#issuecomment-37084601
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 this
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/97#discussion_r10406957
--- Diff: python/pyspark/maxheapq.py ---
@@ -0,0 +1,115 @@
+# -*- coding: latin-1 -*-
+
+"""Heap queue algorithm (a.k.a. priority queue).
+
+#
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/101#issuecomment-37084833
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13056/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/101#issuecomment-37084832
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/92#issuecomment-37084923
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/92#issuecomment-37084924
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 ScrapCodes commented on a diff in the pull request:
https://github.com/apache/spark/pull/97#discussion_r10407050
--- Diff: python/pyspark/maxheapq.py ---
@@ -0,0 +1,115 @@
+# -*- coding: latin-1 -*-
+
+"""Heap queue algorithm (a.k.a. priority queue).
+
Github user koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37085029
"This made all of the old rules not work with newer Hadoop
versions that pull in new asm versions."
curious, what new asm versions were pulled in by newer
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37085083
Newer Hadoop versions pull in ASM 3.1 (through Jersey)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If you
Github user koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37085331
i though the old rule (organization = "asm") would be sufficient to keep
that out? i am clearly missing something, sorry...
---
If your project is set up for it, you
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37085469
That only works when getting Hadoop dependencies by packaging everything in
an uber jar. On yarn, for example, the Hadoop jars and dependencies are pulled
in by pointing to
Github user ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/97#issuecomment-37086086
Hey Matei,
PSF License is included now, I was not sure if the entire history of
license should be included.
---
If your project is set up for it, you can rep
Github user koertkuipers commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37086194
ah got it, thanks. so asm 3.x will be on classpath wether we like it or
not. and we remove all other asm dependencies here, except for a kryo version.
will ch
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/92#issuecomment-37086543
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13057/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/92#issuecomment-37086542
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/97#issuecomment-37086581
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/97#issuecomment-37086582
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/101#issuecomment-37086647
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/80#issuecomment-37086649
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/80#issuecomment-37086650
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/101#issuecomment-37086648
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-37086967
Thanks, merging 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 not have this fe
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37087149
@koertkuipers so I looked at chill and they don't use ASM except inside of
the ClosureCleaner (which they actually borrowed from Spark). Since we don't
use chill's closur
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/80
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/97#issuecomment-37087804
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13058/
---
If your pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/101#issuecomment-37087798
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/101#issuecomment-37087799
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13059/
---
If your p
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/97#issuecomment-37087805
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/80#issuecomment-37087803
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13060/
---
If your pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/97#issuecomment-37087802
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/80#issuecomment-37087801
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/97#issuecomment-37087806
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/101#issuecomment-37088861
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/101#issuecomment-37088862
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-37088856
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13061/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/97#issuecomment-37088855
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/86#issuecomment-37088913
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/86#issuecomment-37088912
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/86#issuecomment-37088937
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13063/
---
If your pr
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/86#issuecomment-37088936
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 t
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/86#issuecomment-37088962
Newest patch includes tests and doc. @pwendell, do you have a link to the
addJar patch? If it's definitely going to happen, I'll take out the
classloader stuff here.
---
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/91#issuecomment-37089032
Upmerged
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/96#issuecomment-37089290
@pwendell Regression test case added, also ensured that the old
implementation fails on this test case.
---
If your project is set up for it, you can reply to this email
GitHub user sryza opened a pull request:
https://github.com/apache/spark/pull/102
SPARK-1064
This reopens PR 649 from incubator-spark against the new repo
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sryza/spark sandy-spark-106
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/101#issuecomment-37089803
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/101#issuecomment-37089804
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13062/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/102#issuecomment-37089813
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/91#issuecomment-37089817
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/91#issuecomment-37089816
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/96#issuecomment-37089815
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-37089812
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/96#issuecomment-37089814
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/96#issuecomment-37090696
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 t
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/96#issuecomment-37090698
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13065/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/102#issuecomment-37090695
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13064/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/102#issuecomment-37090694
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/91#issuecomment-37090699
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13066/
---
If your project i
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/91#issuecomment-37090697
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 t
GitHub user rxin opened a pull request:
https://github.com/apache/spark/pull/103
Allow sbt to use more than 1G of heap.
There was a mistake in sbt build file ( introduced by
012bd5fbc97dc40bb61e0e2b9cc97ed0083f37f6 ) in which we set the default to 2048
and the immediately reset it
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/103#issuecomment-37091259
LGTM
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled an
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/91#issuecomment-37091274
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
e
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/99#issuecomment-37091450
Hey @aarondav this LGTM. Anything else before you can merge this?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub a
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/91
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/103#issuecomment-37091459
Ok I 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 this f
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/96#issuecomment-37091493
@liancheng thanks, looks great! I'll merge 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 pr
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/96#issuecomment-37091522
I decided not to merge this into 0.9... but maybe we could do that later if
there is demand for it.
---
If your project is set up for it, you can reply to this email and
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/103#issuecomment-37091537
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/103#issuecomment-37091538
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/96#issuecomment-37091724
May I ask the reason? I understand that impact of this bug is limited.
---
If your project is set up for it, you can reply to this email and have your
reply appear on Git
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/96#issuecomment-37091891
To be clear, I merged it into master so it will be in Spark 1.0.0. I just
didn't back port it into the 0.9 branch so it won't be in Spark 0.9.1. Usually
we backport things
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/96#issuecomment-37091921
Thanks for the explanation :)
---
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
101 - 196 of 196 matches
Mail list logo
