Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/96
---
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/103
---
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/103#issuecomment-37092461
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/103#issuecomment-37092462
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13067/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/21#issuecomment-37092479
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/21#issuecomment-37092654
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/21#issuecomment-37092655
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13068/
---
If your
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/21#issuecomment-37093324
retest 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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/21#issuecomment-37093423
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/21#issuecomment-37093422
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 rxin opened a pull request:
https://github.com/apache/spark/pull/104
Update junitxml plugin to the latest version to avoid recompilation in
every SBT command.
You can merge this pull request into a Git repository by running:
$ git pull
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/96#issuecomment-37093759
Thanks for this fix - excellent catch !
On Sat, Mar 8, 2014 at 1:53 PM, asfgit notificati...@github.com wrote:
Closed #96
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/21#issuecomment-37094469
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/104#issuecomment-37094472
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/21#issuecomment-37094471
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13069/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/104#issuecomment-37094470
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 holdenk commented on the pull request:
https://github.com/apache/spark/pull/21#issuecomment-37094612
Jenkins, retest 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/21#issuecomment-37094638
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/104#issuecomment-37095429
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/21#issuecomment-37095433
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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/104#issuecomment-37096375
Very cool, finally we have 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/101#issuecomment-37098779
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/101#issuecomment-37098778
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/12#issuecomment-37098783
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/12#issuecomment-37098784
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/105#issuecomment-37100319
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13074/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12#issuecomment-37100324
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-37100327
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13072/
---
If your project
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/104#issuecomment-37104948
LGTM @rxin is there an equivalent thing to this in maven or no? Seems to me
like maybe this is sbt only.
---
If your project is set up for it, you can reply to this
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/105#discussion_r10410220
--- Diff: core/src/main/scala/org/apache/spark/rdd/RDD.scala ---
@@ -666,6 +666,7 @@ abstract class RDD[T: ClassTag](
/**
* Return an array
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/100#issuecomment-37105043
@mateiz this works fine in Java 8 unit tests.
---
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 the pull request:
https://github.com/apache/spark/pull/68#issuecomment-37106963
Do you mind closing this? The solution proposed here isn't going to work
because of the way our docs are compiled. If there is a way to make this work
well in both our
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/16#issuecomment-37107006
@holdenk mind bumping this now that #17 is in? You'll have to change
`extends` to `with`... since the function classes are now interfaces rather
than abstract classes.
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/92#discussion_r10410791
--- Diff: python/pyspark/rdd.py ---
@@ -1057,6 +1058,64 @@ def coalesce(self, numPartitions, shuffle=False):
jrdd =
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/92#discussion_r10410792
--- Diff: python/pyspark/rdd.py ---
@@ -1057,6 +1058,64 @@ def coalesce(self, numPartitions, shuffle=False):
jrdd =
Github user holdenk commented on the pull request:
https://github.com/apache/spark/pull/16#issuecomment-37107763
Sure, I'll give this a shot today :)
On Sat, Mar 8, 2014 at 11:24 AM, Patrick Wendell
notificati...@github.comwrote:
@holdenk
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/92#discussion_r10410905
--- Diff: python/pyspark/rdd.py ---
@@ -1057,6 +1058,64 @@ def coalesce(self, numPartitions, shuffle=False):
jrdd =
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/30#discussion_r10410916
--- Diff: sbin/spark-config.sh ---
@@ -34,3 +34,6 @@ this=$config_bin/$script
export SPARK_PREFIX=`dirname $this`/..
export
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/30#discussion_r10410942
--- Diff: python/Makefile ---
@@ -0,0 +1,7 @@
+assembly: clean
+ python setup.py build --build-lib build/lib
+ unzip lib/py4j*.zip -d
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/30#discussion_r10410971
--- Diff: python/pyspark/java_gateway.py ---
@@ -66,3 +71,30 @@ def run(self):
java_import(gateway.jvm, org.apache.spark.mllib.api.python.*)
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/30#discussion_r10410987
--- Diff: python/pyspark/java_gateway.py ---
@@ -66,3 +71,30 @@ def run(self):
java_import(gateway.jvm, org.apache.spark.mllib.api.python.*)
Github user JoshRosen commented on a diff in the pull request:
https://github.com/apache/spark/pull/30#discussion_r10410991
--- Diff: python/pyspark/java_gateway.py ---
@@ -15,6 +15,7 @@
# limitations under the License.
#
+from glob import glob
--- End diff
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/30#issuecomment-37108992
I left a few minor comments in the diff, but overall this looks good to me.
It might be worth adding build/run instructions in either the PySpark
Programming
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/104#issuecomment-37109170
Ok I merged this.
Not sure about Maven off the top of my head. All these build plugins are
pretty arcane to me.
---
If your project is set up for it, you can
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/30#issuecomment-37109537
@sryza another thing here is, whatever the make target ends up being we
should add it to the `make_release` script and the `make-distribution` script
(those two need to
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/104
---
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/16#issuecomment-37110554
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 opened a pull request:
https://github.com/apache/spark/pull/106
SPARK-1205: Clean up callSite/origin/generator.
This patch removes the `generator` field and simplifies + documents
the tracking of callsites.
There are two places where we care about
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/107
SPARK-1190: Do not initialize log4j if slf4j log4j backend is not being used
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pwendell/spark
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/105#issuecomment-37111528
This doesn't deprecate it in Java (I think). Mind adding that too?
---
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/16#issuecomment-37111991
One or more automated tests failed
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13075/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/107#issuecomment-37111996
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/106#issuecomment-37111998
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/106#issuecomment-37113363
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/106#issuecomment-37113364
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13077/
---
If your project
Evan I actually remembered that Paul Brown (who also reported this
issue) tested it and found that it worked. I'm going to merge this
into master and branch 0.9, so please give it a spin when you have a
chance.
- Patrick
On Sat, Mar 8, 2014 at 2:00 PM, Patrick Wendell pwend...@gmail.com wrote:
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/107#issuecomment-37114184
I've merged this and put it into 0.9. Thanks @prb who tested an earlier
version of this patch.
---
If your project is set up for it, you can reply to this email and
The fix for this was just merged into branch 0.9 (will be in 0.9.1+) and master.
On Sun, Feb 9, 2014 at 11:44 PM, Patrick Wendell pwend...@gmail.com wrote:
Thanks Paul - it isn't mean to be a full solution but just a fix for
the 0.9 branch - for the full solution there is another PR by Sean
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/107
---
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 CodingCat commented on the pull request:
https://github.com/apache/spark/pull/105#issuecomment-37115130
Hi, @pwendell , thank you for the comments
I just fixed that
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/105#issuecomment-37115142
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/105#issuecomment-37115141
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/105#issuecomment-37116110
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13078/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/105#issuecomment-37116109
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/108#issuecomment-37116233
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 opened a pull request:
https://github.com/apache/spark/pull/108
SPARK-1167: Remove metrics-ganglia from default build due to LGPL issues...
This patch removes Ganglia integration from the default build. It
allows users willing to link against LGPL code to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/108#issuecomment-37116234
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 CodingCat commented on the pull request:
https://github.com/apache/spark/pull/12#issuecomment-37116374
@mateiz I have rebased the code, any further comments?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/108#issuecomment-37117121
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13079/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/108#issuecomment-37117125
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/108#issuecomment-37117126
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/108#issuecomment-37118026
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 jyotiska closed the pull request at:
https://github.com/apache/spark/pull/68
---
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/42#issuecomment-37119593
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/42#issuecomment-37119592
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 this
GitHub user kellrott opened a pull request:
https://github.com/apache/spark/pull/109
Ability to initialize Spark-Shell with command script
This script allows a user to define a script file with code that will be
executed when then spark-shell starts up.
This initialization
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/109#issuecomment-37120323
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/42#issuecomment-37120318
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/109#issuecomment-37121124
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/13082/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/109#issuecomment-37121123
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 qqsun8819 opened a pull request:
https://github.com/apache/spark/pull/110
SPARK-1099:Spark's local mode should probably respect spark.cores.max by
default
This is for JIRA:https://spark-project.atlassian.net/browse/SPARK-1099
And this is what I do in this patch
81 matches
Mail list logo
