Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/341#issuecomment-40300457
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/341#issuecomment-40300470
Alright, I think this is ready to go now. I've updated the docs to mention
sparse vectors and updated the Python examples to use LabeledPoint as well. CC
@mengxr
---
If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/341#issuecomment-40300460
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 mateiz commented on the pull request:
https://github.com/apache/spark/pull/363#issuecomment-40300482
Is this failing due to not cleaning up some files?
---
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 mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/383#discussion_r11563442
--- Diff: python/pyspark/java_gateway.py ---
@@ -38,12 +38,19 @@ def launch_gateway():
# Don't send ctrl-c / SIGINT to the Java gateway:
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/341#issuecomment-40300926
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14090/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/341#issuecomment-40300925
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 berngp commented on the pull request:
https://github.com/apache/spark/pull/355#issuecomment-40301034
@pwendell Mesos 0.16.0 uses protobufs 2.4.1 while Mesos 0.17.0 and above
upgraded to 2.5.0. On the other hand Hadoop 1.4 uses protobufs 2.4.1 while
Hadoop 2.2+ upgraded
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/391#issuecomment-40301185
Just verified with numpy 1.6.2. All 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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/391#issuecomment-40301392
@mengxr yupp works with 1.4, 1.5 too :+1:
---
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 opened a pull request:
https://github.com/apache/spark/pull/398
SPARK-1480: Clean up use of classloaders
The Spark codebase is a bit fast-and-loose when accessing classloaders and
this has caused a few bugs to surface in master.
This patch defines
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/341#issuecomment-40301544
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/398#issuecomment-40301543
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/341#issuecomment-40301546
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/398#issuecomment-40301545
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/376#issuecomment-40301820
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/376#issuecomment-40301822
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/357#issuecomment-40301947
@srowen mind reviewing the PR?
---
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/398#issuecomment-40302133
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14091/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/398#issuecomment-40302132
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/360#issuecomment-40302375
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/360#issuecomment-40302378
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 abhishekkr commented on the pull request:
https://github.com/apache/spark/pull/392#issuecomment-40302502
@mateiz handling it from Python would error out after entering initiating
Python once and logging it out, thus didn't solved it that way... though that
style is
GitHub user abhishekkr opened a pull request:
https://github.com/apache/spark/pull/399
[python alternative] pyspark require Python2, failing if system default is
Py3 from shell.py
Python alternative for https://github.com/apache/spark/pull/392; managed
from shell.py
You can merge
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/399#issuecomment-40302542
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/360#issuecomment-40302781
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/360#issuecomment-40302779
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/341#issuecomment-40302965
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/341#issuecomment-40302966
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14092/
---
If your project is set up for it, you can
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/304#issuecomment-40303204
Thanks for taking a look @mengxr. Working on a patch that addresses the
inline comments. On the broader points:
We should spend more time on the data types.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/360#issuecomment-40303296
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14094/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/376#issuecomment-40303293
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/376#issuecomment-40303295
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14093/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/360#issuecomment-40303294
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/360#issuecomment-40303420
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14095/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/360#issuecomment-40303419
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 kanzhang commented on the pull request:
https://github.com/apache/spark/pull/306#issuecomment-40303520
test
---
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
GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/400
SPARK-1482: Fix potential resource leaks in saveAsHadoopDataset and save...
...AsNewAPIHadoopDataset
JIRA: https://issues.apache.org/jira/browse/SPARK-1482
You can merge this pull request
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/400#issuecomment-40304469
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/151#issuecomment-40304490
This is the same issue reported in
https://issues.apache.org/jira/browse/SPARK-1479
---
If your project is set up for it, you can reply to this email and have your
reply
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/357#issuecomment-40304539
I myself don't agree with this change, no. See the discussion in
https://issues.apache.org/jira/browse/SPARK-1441 . For example, I think you can
merely build with the
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/397#issuecomment-40304662
Yeah this looks a lot like what I personally have in mind. I think you
could simply subclass `java.io.ByteArrayOutputStream` and add the two new
methods, to avoid writing
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/357#issuecomment-40304913
So, if someone compile the spark with hadoop 0.23.x how to automatically
activate the profile
```xml
profile
idyarn-alpha/id
dependencies
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/357#issuecomment-40305010
Right, but you can just write `-Pyarn-alpha` and set `hadoop.version` and
`yarn.version` as you like. That gets what you need.
A better change would be to change
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/357#issuecomment-40305799
```xml
activation
propertynamehadoop.version/namevalue[0.23,0.24)/value/property
/activation
```
It doesn't work
see
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/357#issuecomment-40305906
That's not quite what I mean. `hadoop.version` affects the version of the
various artifacts in the build of course, like `hadoop-client`. You can express
activations based
Github user yinxusen commented on the pull request:
https://github.com/apache/spark/pull/376#issuecomment-40307008
Well.. I got this two wired errors. Build time out.
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/376#issuecomment-40310494
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/376#issuecomment-40310519
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/398#issuecomment-40310789
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/398#issuecomment-40311057
Okay I'm probably gonna merge this because it's blocking some QA work.
@manku-timma if you could check that Mesos is still okay with this patch that
would be great...
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/376#issuecomment-40311539
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/376#issuecomment-40311540
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14096/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/398
---
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 techaddict commented on the pull request:
https://github.com/apache/spark/pull/388#issuecomment-40312774
@pwendell is there something else you were expecting ?
---
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/360#issuecomment-40312907
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/360#issuecomment-40312900
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/398#issuecomment-40313223
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/398#issuecomment-40313224
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14097/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/360#issuecomment-40313465
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/360#issuecomment-40313462
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/360#issuecomment-40313974
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/360#issuecomment-40313975
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14098/
---
If your project
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/341#issuecomment-40315299
Jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/341#issuecomment-40315406
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/341#issuecomment-40315411
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/360#issuecomment-40316176
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/360#issuecomment-40316177
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14099/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/341#issuecomment-40316534
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/341#issuecomment-40316536
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14100/
---
If your project
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/397#issuecomment-40316654
Eh the other reason fastutil implements the FastByteArrayOutputStream
without subclassing ByteArrayOutputStream was to get rid of the synchronized
writes. To do this
Github user pwendell closed the pull request at:
https://github.com/apache/spark/pull/119
---
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 srowen commented on the pull request:
https://github.com/apache/spark/pull/397#issuecomment-40317255
Yes, even if the lock is not removed (and it should be) its overhead is
trivial compared to other operations here. Up to you.
---
If your project is set up for it, you
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/376#issuecomment-40318472
Thanks Xusen! I've merged this in.
---
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 kanzhang opened a pull request:
https://github.com/apache/spark/pull/401
Fixing a race condition in event listener unit test
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kanzhang/spark fix-1475
Alternatively you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/401#issuecomment-40318997
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 kanzhang commented on the pull request:
https://github.com/apache/spark/pull/366#issuecomment-40319077
@pwendell @andrewor14 , I think the unit test depends on a race condition
that the stopper thread is run before the listener thread does (but we don't
know the actual
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/299#discussion_r11567194
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ClientBase.scala ---
@@ -340,8 +341,22 @@ trait ClientBase extends Logging {
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/299#discussion_r11567219
--- Diff:
yarn/common/src/main/scala/org/apache/spark/deploy/yarn/ClientBase.scala ---
@@ -340,8 +341,22 @@ trait ClientBase extends Logging {
Github user pwendell commented on a diff in the pull request:
https://github.com/apache/spark/pull/299#discussion_r11567397
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/cluster/SparkDeploySchedulerBackend.scala
---
@@ -42,11 +42,16 @@ private[spark] class
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/376
---
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/397#issuecomment-40320307
Apparently the JVM implements biased locking
(http://www.oracle.com/technetwork/java/6-performance-137236.html#2.1.1) when
an object's monitor is uncontended, which
Github user aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/397#discussion_r11567459
--- Diff:
core/src/main/scala/org/apache/spark/util/io/FastByteArrayOutputStream.scala ---
@@ -0,0 +1,113 @@
+/*
+ * Licensed to the Apache Software
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/397#issuecomment-40320487
Yes I knew about biased locking. That's why I said how well the jvm can do
away with the lock that is always running in a single threaded mode. However,
it is hard to test
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/397#issuecomment-40320605
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/397#issuecomment-40320613
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/299#issuecomment-40321268
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 CodingCat commented on the pull request:
https://github.com/apache/spark/pull/339#issuecomment-40321243
Hi, @kayousterhout, you mean just split the test cases and move some of
them to another file?
I can do that...but do you think the test cases specific to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/299#issuecomment-40321272
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/299#issuecomment-40321304
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/299#issuecomment-40321305
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14102/
---
If your project is set up for it, you can
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/389#discussion_r11568224
--- Diff: docs/configuration.md ---
@@ -96,7 +96,13 @@ Apart from these, the following properties are also
available, and may be useful
trthProperty
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/397#issuecomment-40321666
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/397#issuecomment-40321667
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14101/
---
If your project
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/60#issuecomment-40321699
It seems that some executors are crashing. Can you go to the first Lost
TID messages in the log, see which nodes they were on, and look at those
executors' logs? It may
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/400#issuecomment-40321730
Jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/401#issuecomment-40321766
Jenkins, test this please
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/400#issuecomment-40321816
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/401#issuecomment-40321813
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/400#issuecomment-40321810
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
1 - 100 of 132 matches
Mail list logo
