Github user lamuguo commented on a diff in the pull request:
https://github.com/apache/spark/pull/867#discussion_r13217796
--- Diff: core/src/main/scala/org/apache/spark/Aggregator.scala ---
@@ -32,7 +33,8 @@ import org.apache.spark.util.collection.{AppendOnlyMap,
Github user lamuguo commented on a diff in the pull request:
https://github.com/apache/spark/pull/867#discussion_r13217800
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/Aggregate.scala ---
@@ -155,48 +155,60 @@ case class Aggregate(
}
} else
Github user lamuguo commented on a diff in the pull request:
https://github.com/apache/spark/pull/867#discussion_r13217803
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/Aggregate.scala ---
@@ -155,48 +155,60 @@ case class Aggregate(
}
} else
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/904
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/910#issuecomment-44618741
Hey actually, on second thought. We can merge this. But do you mind setting
previousArtifact equal to Spark 1.0.0 everywhere? We've now published the 1.0.0
artifacts to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/910#issuecomment-44620616
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/910#issuecomment-44621165
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/910#issuecomment-44621179
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/772#issuecomment-44621757
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/772#issuecomment-44621766
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/896
---
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 pwendell commented on the pull request:
https://github.com/apache/spark/pull/896#issuecomment-44622890
Thanks Matei, I've merged 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/910#issuecomment-44623129
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15298/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/910#issuecomment-44623817
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15299/
---
If your project
Github user mridulm commented on a diff in the pull request:
https://github.com/apache/spark/pull/894#discussion_r13220194
--- Diff:
yarn/alpha/src/main/scala/org/apache/spark/deploy/yarn/ExecutorLauncher.scala
---
@@ -92,21 +92,22 @@ class ExecutorLauncher(args:
Github user mridulm commented on the pull request:
https://github.com/apache/spark/pull/894#issuecomment-44625937
hey @sryza did we also add overhead for workers too ? iirc I had added it
only for master.
Do we need two different values for both ? Since the performance
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-44626030
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 kalpit opened a pull request:
https://github.com/apache/spark/pull/918
SPARK-1972: Added support for tracking custom task-related metrics
Any piece of Spark machinery that cares to track custom task-related
metrics can now use the setCustomMetric(name,value) method on
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/918#issuecomment-44629724
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/772#issuecomment-44630478
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/772#issuecomment-44630491
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/909#issuecomment-44633797
@marmbrus Just rebased this PR to the latest master branch (optimized
`HiveTableScan` operator included).
---
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/909#issuecomment-44633943
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/909#issuecomment-44633955
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/772#issuecomment-44637439
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15301/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/772#issuecomment-44637438
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/909#issuecomment-44638297
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/772#issuecomment-44639146
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/772#issuecomment-44639160
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 srowen opened a pull request:
https://github.com/apache/spark/pull/919
SPARK-1973. Add randomSplit to JavaRDD (with tests, and tidy Java tests)
I'd like to use randomSplit through the Java API, and would like to add a
convenience wrapper for this method to JavaRDD. This
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/919#issuecomment-44642038
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/772#issuecomment-44644086
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15303/
---
If your project is set up for it, you can
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/919#issuecomment-44644854
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15304/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/919#issuecomment-44644853
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 witgo commented on a diff in the pull request:
https://github.com/apache/spark/pull/655#discussion_r13227671
--- Diff:
yarn/stable/src/main/scala/org/apache/spark/deploy/yarn/YarnAllocationHandler.scala
---
@@ -105,278 +96,222 @@ private[yarn] class
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44649192
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/920#issuecomment-44649200
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 srowen opened a pull request:
https://github.com/apache/spark/pull/920
SPARK-1806 (addendum) Use non-deprecated methods in Mesos 0.18
The update to Mesos 0.18 caused some deprecation warnings in the build. The
change to the non-deprecated version is straightforward as
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/920#issuecomment-44649359
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/920#issuecomment-44649361
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15305/
---
If your project is set up for it, you can
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/894#issuecomment-44666824
Workers currently get 384 added as well (see
YarnAllocationHandler.MEMORY_OVERHEARD). At a first approximation, this seems
reasonable to me. The AM and executors are both
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/921
In some cases, yarn does not automatically restart the container
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/witgo/spark allocateExecutors
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/921#issuecomment-44668452
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/921#issuecomment-44668465
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 sryza commented on the pull request:
https://github.com/apache/spark/pull/921#issuecomment-44669121
This is already handles in ExecutorLauncher.launchReporterThread and
ApplicationMaster.launchReporterThread, no?
---
If your project is set up for it, you can reply to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/921#issuecomment-44672762
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/921#issuecomment-44672764
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15306/
---
If your project
GitHub user aarondav opened a pull request:
https://github.com/apache/spark/pull/922
SPARK-1839: PySpark RDD#take() shouldn't always read from driver
This patch simply ports over the Scala implementation of RDD#take(), which
reads the first partition at the driver, then decides how
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/922#issuecomment-44674829
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/922#issuecomment-44674842
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 aarondav commented on the pull request:
https://github.com/apache/spark/pull/854#issuecomment-44675428
Merged into master and branch-1.0. 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 nchammas opened a pull request:
https://github.com/apache/spark/pull/923
updated link to mailing list
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nchammas/spark patch-1
Alternatively you can review and apply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/923#issuecomment-44676470
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/922#issuecomment-44679192
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15307/
---
If your project
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/922#issuecomment-44679190
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 a diff in the pull request:
https://github.com/apache/spark/pull/776#discussion_r13241563
--- Diff:
core/src/main/scala/org/apache/spark/rdd/ParallelCollectionRDD.scala ---
@@ -128,18 +137,17 @@ private object ParallelCollectionRDD {
Github user kanzhang commented on a diff in the pull request:
https://github.com/apache/spark/pull/755#discussion_r13241708
--- Diff: python/pyspark/context.py ---
@@ -51,6 +51,7 @@ class SparkContext(object):
_active_spark_context = None
_lock = Lock()
GitHub user CodingCat opened a pull request:
https://github.com/apache/spark/pull/924
SPARK-1976: update streaming docs
Spark streaming requires at least two working thread, but the document
gives the example like
import org.apache.spark.api.java.function._
import
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/924#issuecomment-44683676
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/924#issuecomment-44683692
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 kanzhang commented on the pull request:
https://github.com/apache/spark/pull/755#issuecomment-44685162
@mateiz I already have some tests on saveAsPickleFile method, which uses
both pickFile and saveAsPickleFile. What more test cases do you have in mind? I
could add one
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/924#issuecomment-44688156
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/924#issuecomment-44688158
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15308/
---
If your project
GitHub user nevillelyh opened a pull request:
https://github.com/apache/spark/pull/925
[SPARK-1977][MLLIB] use immutable BitSet in ALS
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nevillelyh/spark branch-1.0
Alternatively
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/925#issuecomment-44690150
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 opened a pull request:
https://github.com/apache/spark/pull/926
SPARK-1974. Most examples fail at startup because spark.master is not set
Most example code has a few lines like:
```
val sparkConf = new SparkConf().setAppName(Foo)
val sc = new
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44703759
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/926#issuecomment-44703748
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 vanzin commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44704211
Won't this break things if you try to submit the examples with spark-submit
(which I think is the New And Approved Way (tm))?
spark-submit will set spark.master,
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44704420
Hm good question, you could make it work with `-Dspark.master=...`. This
would overwrite those settings. It seems like the examples are intended to work
without that
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44706840
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/926#issuecomment-44706841
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15309/
---
If your project is set up for it, you can
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/917#issuecomment-44710024
BTW I have a different version of the fix that changes RandomSamplerSuite /
CacheManagerSuite to use mockito instead of easymock. Mockito doesn't seem to
suffer from the
Github user vanzin commented on the pull request:
https://github.com/apache/spark/pull/926#issuecomment-44713032
If you really want to keep the tests working outside of spark-submit, I'd
suggest using the SparkContext(SparkConf) constructor instead, and using
SparkConf.setIfMissing()
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/927#issuecomment-44713343
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 ash211 opened a pull request:
https://github.com/apache/spark/pull/927
Typo: and - an
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ash211/spark patch-5
Alternatively you can review and apply these changes as the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/927#issuecomment-44713349
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 ankurdave commented on the pull request:
https://github.com/apache/spark/pull/10#issuecomment-44714289
ok to 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10#issuecomment-44714354
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/10#issuecomment-44714350
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/927#issuecomment-44714464
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/927#issuecomment-44714465
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15310/
---
If your project
Github user dorx commented on the pull request:
https://github.com/apache/spark/pull/916#issuecomment-44714674
@mengxr ping
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10#issuecomment-44715244
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. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10#issuecomment-44715245
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15311/
---
If your project
Github user ankurdave commented on the pull request:
https://github.com/apache/spark/pull/10#issuecomment-44715274
@andy327 This looks good to me, aside from some minor style and type
signature changes that I made in tresata/spark#2. Could you merge that? Then I
can finally merge
Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/909#issuecomment-44715351
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/909#issuecomment-44715435
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/909#issuecomment-44715431
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/909#issuecomment-44716639
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/909#issuecomment-44716640
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15312/
---
If your project
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/927#issuecomment-44718161
Thanks. Merged in 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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/927
---
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/925#issuecomment-44718196
Maybe we should just make sure the mutable bitsets are registered instead
of doing the conversion?
---
If your project is set up for it, you can reply to this email and
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/923#issuecomment-44718204
Thanks. I've merged this in 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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/924#issuecomment-44718218
Thanks - merged in 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 asfgit closed the pull request at:
https://github.com/apache/spark/pull/923
---
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/924
---
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 a diff in the pull request:
https://github.com/apache/spark/pull/914#discussion_r13259381
--- Diff:
core/src/main/scala/org/apache/spark/deploy/SparkSubmitArguments.scala ---
@@ -381,16 +381,19 @@ private[spark] class SparkSubmitArguments(args:
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/912#issuecomment-44718299
I'm merging 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
1 - 100 of 102 matches
Mail list logo
