Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/685#issuecomment-43137270
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/779#issuecomment-4314
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 commented on the pull request:
https://github.com/apache/spark/pull/700#issuecomment-42636403
LGTM. Any idea how big closure sizes might grow?
---
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/676
SPARK-1746: Support setting SPARK_JAVA_OPTS on executors for backwards
compatibility
You can merge this pull request into a Git repository by running:
$ git pull
Github user lianhuiwang commented on a diff in the pull request:
https://github.com/apache/spark/pull/636#discussion_r12464105
--- Diff:
core/src/main/scala/org/apache/spark/deploy/ApplicationDescription.scala ---
@@ -28,6 +28,7 @@ private[spark] class ApplicationDescription(
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/675#issuecomment-42400544
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14763/
---
If your project is set up for it, you can
Github user darose commented on the pull request:
https://github.com/apache/spark/pull/629#issuecomment-42602116
I tried building an running this code, but it failed with:
14/05/08 20:09:11 ERROR Remoting:
org.apache.spark.deploy.ApplicationDescription; local class
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/717#discussion_r12497536
--- Diff:
core/src/test/scala/org/apache/spark/util/ClosureCleanerSuite.scala ---
@@ -108,6 +117,20 @@ class TestClassWithoutFieldAccess {
}
}
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/552#discussion_r12388585
--- Diff:
examples/src/main/scala/org/apache/spark/examples/graphx/LiveJournalPageRank.scala
---
@@ -44,6 +44,6 @@ object LiveJournalPageRank {
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/675#issuecomment-42491108
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/675
---
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/656
---
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/680#issuecomment-42403127
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/622#issuecomment-42697084
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 aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/603#discussion_r12391211
--- Diff:
core/src/main/scala/org/apache/spark/api/python/PythonWorkerFactory.scala ---
@@ -208,6 +170,19 @@ private[spark] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/475#issuecomment-42497745
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/640#issuecomment-42452187
Okay I did a quick pass and this looks good. I'm going to pull this in.
Thanks @aarondav!
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/552#issuecomment-42518042
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/799#issuecomment-43282663
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/692#issuecomment-43247738
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/801#issuecomment-43287421
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/760#issuecomment-43264224
Looked a little further, it seems once a seq is sliced into partitions,
those partitions are no longer sequences. To find partition length, one has to
iterate through
GitHub user vanzin opened a pull request:
https://github.com/apache/spark/pull/794
Remove compile-scoped junit dependency.
This avoids having junit classes showing up in the assembly jar.
I verified that only test classes in the jtransforms package
use junit.
You can merge
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/787#issuecomment-43181035
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15023/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/788#issuecomment-43177436
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 huajianmao opened a pull request:
https://github.com/apache/spark/pull/798
A typo in the TaskSchedulerImpl
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/huajianmao/spark patch-1
Alternatively you can review and
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/769#issuecomment-43279633
Do you mind adding a unit test for 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/787#issuecomment-43177125
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 commented on a diff in the pull request:
https://github.com/apache/spark/pull/446#discussion_r12707068
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -114,13 +120,19 @@ case class Or(left: Expression,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/787#issuecomment-43181033
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/799#issuecomment-43286838
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15036/
---
If your project
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/446#issuecomment-43287508
LGTM. I will merge it once Jenkins comes back green.
---
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 aarondav opened a pull request:
https://github.com/apache/spark/pull/800
SPARK-1860: Do not cleanup application work/ directories by default
This causes an unrecoverable error for applications that are running for
longer
than 7 days that have jars added to the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/794#issuecomment-43253650
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/795#issuecomment-43263384
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/793#issuecomment-43238041
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 commented on a diff in the pull request:
https://github.com/apache/spark/pull/446#discussion_r12707082
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/expressions/predicates.scala
---
@@ -133,8 +145,12 @@ case class Equals(left: Expression,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/792#issuecomment-43239147
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/788#issuecomment-43279696
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
Github user xiliu82 commented on the pull request:
https://github.com/apache/spark/pull/796#issuecomment-43260264
This is to fix a bug where apply Hive UDF on a struct, it will throw
NoMatch exception.
---
If your project is set up for it, you can reply to this email and have your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/771#issuecomment-43181483
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 sryza opened a pull request:
https://github.com/apache/spark/pull/795
SPARK-1851. Upgrade Avro dependency to 1.7.6 so Spark can read Avro file...
...s
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sryza/spark
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/800#issuecomment-43285316
@aarondav what about just not cleaning up the data if the app is still
running? In the future we should probably assess the TTL based on the finish
time of the app, not
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/692#issuecomment-43277668
Alright mind closing this 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/788#issuecomment-43180318
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15020/
---
If your project
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/739
---
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/800#issuecomment-43285803
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15035/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/446#issuecomment-43287373
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/796#issuecomment-43269860
Can you add a test case? Or maybe find a HiveTest case that can be
whitelisted in HiveCompatibilitySuite?
---
If your project is set up for it, you can reply to this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/789#issuecomment-43179185
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/798
---
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/787#issuecomment-43259205
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/802#issuecomment-43288334
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/798#issuecomment-43282298
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/771#issuecomment-43178406
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/799
[SPARK-1808] Route bin/pyspark through Spark submit
**Problem.** For `bin/pyspark`, there is currently no other way to specify
Spark configuration properties other than through `SPARK_JAVA_OPTS`
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/787#issuecomment-43256128
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/797#issuecomment-43278874
Thanks. Merged into master branch-1.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
GitHub user ArcherShao opened a pull request:
https://github.com/apache/spark/pull/792
Add a function that can build an EdgePartition faster.
If user can make sure every edge add by the order, use this function to
build an EdgePartition will be faster.
You can merge this pull
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/670
---
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/790#issuecomment-43246060
Thanks. Merged into master branch-1.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/794#issuecomment-43280215
@vanzin Did you check the sbt side? Try `sbt/sbt assembly` and see whether
we have junit classes inside?
---
If your project is set up for it, you can reply to this email
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/771#issuecomment-43178416
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 commented on the pull request:
https://github.com/apache/spark/pull/795#issuecomment-43260775
Ah - sorry I see there is information in the JIRA
---
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/787#issuecomment-43177758
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15019/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/701#issuecomment-42620554
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/708#issuecomment-42631837
Looks like we already `ask` for other messages we send to the slave actor.
LGTM.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/639#issuecomment-42726700
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 tgravescs commented on the pull request:
https://github.com/apache/spark/pull/649#issuecomment-42456933
Its ready to go.
---
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 scwf closed the pull request at:
https://github.com/apache/spark/pull/695
---
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/683#issuecomment-42481057
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/701#discussion_r12457925
--- Diff: docs/running-on-yarn.md ---
@@ -43,18 +43,19 @@ Unlike in Spark standalone and Mesos mode, in which the
master's address is spec
To
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/639#issuecomment-42705008
@markhamstra Further testing (test code
[here](https://gist.github.com/aarondav/ca1f0cdcd50727f89c0d)) seems to
indicate that the uncaughtExceptionHandler is **not**
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/546#issuecomment-42456863
Just my 2 bits, but using getCanonicalPath() is usually a code smell;
unless it's explicitly necessary (i.e. you know you have a symlink and you want
to remove the actual
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/622#issuecomment-42700861
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14849/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/700#issuecomment-42610619
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/789#issuecomment-43182223
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15022/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/787#issuecomment-43259206
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15030/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/787#issuecomment-43177756
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/799#issuecomment-43283363
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 rxin commented on the pull request:
https://github.com/apache/spark/pull/769#issuecomment-43279644
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 ScrapCodes commented on the pull request:
https://github.com/apache/spark/pull/771#issuecomment-43178109
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
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-43175575
Hey @ScrapCodes - this looks like a good start. In terms of how to pass
options I think the nicest behavior would be to just make it identical to maven:
```
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/800#issuecomment-43283009
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/802#issuecomment-43288328
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/769#issuecomment-43303370
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/795#issuecomment-43263385
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15031/
---
If your project
GitHub user ScrapCodes opened a pull request:
https://github.com/apache/spark/pull/788
Update package-info.java
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ScrapCodes/spark-1 patch-1
Alternatively you can review and apply
Github user zhpengg commented on the pull request:
https://github.com/apache/spark/pull/769#issuecomment-43290434
ut added. @rxin
---
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 ankurdave commented on a diff in the pull request:
https://github.com/apache/spark/pull/497#discussion_r12453849
--- Diff:
graphx/src/main/scala/org/apache/spark/graphx/impl/EdgePartition.scala ---
@@ -17,39 +17,86 @@
package org.apache.spark.graphx.impl
GitHub user cloud-fan opened a pull request:
https://github.com/apache/spark/pull/791
improve performance of MemoryStore#tryToPut by elimating unnecessary lock
It's unefficient to drop memory blocks to disk inside a synchronized block
as IO is slow. As the TODO says, we just need
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/790#issuecomment-43245088
Nice. We stopped using this before because it was breaking serialization
of Rows (since they are also Seqs). I guess as long as we run it after
registering Rows
Github user kanzhang commented on a diff in the pull request:
https://github.com/apache/spark/pull/776#discussion_r12706894
--- Diff:
core/src/main/scala/org/apache/spark/rdd/ParallelCollectionRDD.scala ---
@@ -128,18 +137,17 @@ private object ParallelCollectionRDD {
Github user dongwang218 commented on a diff in the pull request:
https://github.com/apache/spark/pull/643#discussion_r12463267
--- Diff: mllib/src/main/scala/org/apache/spark/mllib/util/MLUtils.scala ---
@@ -76,7 +76,7 @@ object MLUtils {
} else {
parsed.map {
Github user nishkamravi2 commented on the pull request:
https://github.com/apache/spark/pull/692#issuecomment-43276933
Yeah, this test is now passing (without my change). Something got fixed
since this PR was initiated last week.
---
If your project is set up for it, you can reply
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/448#issuecomment-42393027
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 aarondav commented on a diff in the pull request:
https://github.com/apache/spark/pull/603#discussion_r12387647
--- Diff:
core/src/main/scala/org/apache/spark/api/python/PythonWorkerFactory.scala ---
@@ -208,6 +170,19 @@ private[spark] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/787#issuecomment-43255242
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/800#issuecomment-43282996
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/701#issuecomment-42716829
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14855/
---
If your project
1 - 100 of 430 matches
Mail list logo
