Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1477#issuecomment-49501450
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 fireflyc commented on the pull request:
https://github.com/apache/spark/pull/1485#issuecomment-49501533
My program is spark streaming over Hadoop yarn.It work for user click
stream.
I read code,number of worker threads and block?
---
If your project is set up for it,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1477#issuecomment-49501569
QA tests have started for PR 1477. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16842/consoleFull
---
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1488#issuecomment-49501577
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
Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/1488#issuecomment-49501586
Jenkins, retest this *pretty* 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
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1452#issuecomment-49501642
Thanks for taking a look. I'm merging this one as is, and will submit a
small PR to fix the issues.
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1488#issuecomment-49501654
QA tests have started for PR 1488. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16843/consoleFull
---
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1452#discussion_r15142372
--- Diff: core/src/main/scala/org/apache/spark/scheduler/ResultTask.scala
---
@@ -17,134 +17,68 @@
package org.apache.spark.scheduler
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/1439#issuecomment-49501954
As for benchmarks, the micro benchmark code comes with #758 may be helpful.
And I feel that partitioning support for Parquet should be considered together
with the
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1292#issuecomment-49502313
QA tests have started for PR 1292. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16844/consoleFull
---
GitHub user mengxr opened a pull request:
https://github.com/apache/spark/pull/1492
[SPARK-2495][MLLIB] remove private[mllib] from linear models' constructors
This is part of SPARK-2495 to allow users construct linear models manually.
You can merge this pull request into a Git
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1477#issuecomment-49503177
QA results for PR 1477:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1492#issuecomment-49503225
QA tests have started for PR 1492. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16845/consoleFull
---
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1477#issuecomment-49503209
Thanks. Merging in master.
---
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/1477
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1488#issuecomment-49503309
QA results for PR 1488:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
GitHub user mengxr opened a pull request:
https://github.com/apache/spark/pull/1493
[SPARK-2552][MLLIB] stabilize logistic function in pyspark
to avoid overflow in `exp(x)` if `x` is large.
You can merge this pull request into a Git repository by running:
$ git pull
Github user maji2014 closed the pull request at:
https://github.com/apache/spark/pull/1457
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1493#issuecomment-49504244
QA tests have started for PR 1493. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16847/consoleFull
---
GitHub user maji2014 opened a pull request:
https://github.com/apache/spark/pull/1494
Required AM memory is amMem, not args.amMemory
ERROR yarn.Client: Required AM memory (1024) is above the max threshold
(1048) of this cluster appears if this code is not changed. obviously, 1024
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1494#issuecomment-49506353
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/940#issuecomment-49508061
QA tests have started for PR 940. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16848/consoleFull
---
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1442
---
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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/1442#issuecomment-49513281
Thanks! I've merged this into master.
---
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
Github user witgo commented on the pull request:
https://github.com/apache/spark/pull/1409#issuecomment-49513420
@aarondav @pwendell
In my tests, it seems that there are still a deadlock.
To find a possible reason this here [Executor.scala#L189]
Github user mengxr commented on the pull request:
https://github.com/apache/spark/pull/1493#issuecomment-49515870
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 mengxr commented on the pull request:
https://github.com/apache/spark/pull/1492#issuecomment-49515873
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1492#issuecomment-49515905
QA tests have started for PR 1492. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16850/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1493#issuecomment-49515915
QA tests have started for PR 1493. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16849/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1165#issuecomment-49516746
QA tests have started for PR 1165. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16851/consoleFull
---
Github user aarondav commented on the pull request:
https://github.com/apache/spark/pull/1485#issuecomment-49526386
@fireflyc Spark should not be scheduling more than N concurrent tasks on an
Executor. It appears that the tasks may be returning success but then don't
actually return
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1387#issuecomment-49527449
QA tests have started for PR 1387. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16852/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1482#issuecomment-49527553
QA tests have started for PR 1482. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16853/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1482#issuecomment-49527623
QA results for PR 1482:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/1165#discussion_r15145476
--- Diff:
core/src/main/scala/org/apache/spark/util/collection/SizeTrackingAppendOnlyBuffer.scala
---
@@ -0,0 +1,43 @@
+/*
+ * Licensed to the Apache
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1482#issuecomment-49527896
QA tests have started for PR 1482. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16854/consoleFull
---
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1490#discussion_r15145612
--- Diff:
core/src/main/scala/org/apache/spark/network/MessageChunkHeader.scala ---
@@ -41,6 +42,13 @@ private[spark] class MessageChunkHeader(
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/1490#discussion_r15145614
--- Diff:
core/src/main/scala/org/apache/spark/network/MessageChunkHeader.scala ---
@@ -67,13 +75,20 @@ private[spark] object MessageChunkHeader {
val
Github user sarutak commented on the pull request:
https://github.com/apache/spark/pull/1490#issuecomment-49528521
Thanks @rxin I'll try it.
---
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/1495#issuecomment-49529878
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 cesararevalo opened a pull request:
https://github.com/apache/spark/pull/1495
Typo fix to the programming guide in the docs
Typo fix to the programming guide in the docs. Changed the word
distibuted to distributed.
You can merge this pull request into a Git repository
Github user mburke13 commented on the pull request:
https://github.com/apache/spark/pull/1290#issuecomment-49531526
@bgreeven Are you continuing work on this pull request so that it passes
all unit tests?
---
If your project is set up for it, you can reply to this email and have
GitHub user pwendell opened a pull request:
https://github.com/apache/spark/pull/1496
SPARK-2596 A tool for mirroring github pull requests on JIRA.
For a bunch of reasons we should automatically populate a JIRA with
information about new pull requests when they arrive. I've written
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1496#issuecomment-49532480
QA tests have started for PR 1496. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16855/consoleFull
---
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/1452#issuecomment-49532568
Apparently this broke the build. Reverting and will work on a fix.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1452#issuecomment-49532564
@rxin @mateiz this has broken the master build so we should revert it. If
you look here there was never actually a success message from SparkQA - I
think the tests are
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1496#issuecomment-49532713
QA tests have started for PR 1496. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16856/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1496#issuecomment-49533119
QA tests have started for PR 1496. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16857/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1496#issuecomment-49533420
QA tests have started for PR 1496. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16858/consoleFull
---
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1496#issuecomment-49533533
QA tests have started for PR 1496. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16859/consoleFull
---
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1496
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1496#issuecomment-49534890
QA results for PR 1496:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user mateiz commented on the pull request:
https://github.com/apache/spark/pull/1452#issuecomment-49534978
Hah, the new Spark QA messages are really confusing! Is there no timeout on
the build?
---
If your project is set up for it, you can reply to this email and have your
GitHub user willb opened a pull request:
https://github.com/apache/spark/pull/1497
SPARK-2226: transform HAVING clauses with unresolvable attributes
This commit adds an analyzer rule to
1. find expressions in `HAVING` clause filters that depend on unresolved
attributes,
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1497#issuecomment-49535141
QA tests have started for PR 1497. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16860/consoleFull
---
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1495
---
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/1489#issuecomment-49535984
Ah, good catch. This was my mistake. Thanks for this! I'll merge it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1489
---
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 mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/1165#discussion_r15147416
--- Diff:
core/src/main/scala/org/apache/spark/util/collection/SizeTrackingAppendOnlyBuffer.scala
---
@@ -0,0 +1,43 @@
+/*
+ * Licensed to the Apache
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/1165#discussion_r15147419
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -463,16 +463,15 @@ private[spark] class BlockManager(
val
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/1165#discussion_r15147423
--- Diff: core/src/main/scala/org/apache/spark/storage/BlockManager.scala
---
@@ -463,16 +463,15 @@ private[spark] class BlockManager(
val
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1474#issuecomment-49536204
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 mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/1165#discussion_r15147427
--- Diff: core/src/main/scala/org/apache/spark/CacheManager.scala ---
@@ -140,14 +145,36 @@ private[spark] class CacheManager(blockManager:
BlockManager)
Github user mateiz commented on a diff in the pull request:
https://github.com/apache/spark/pull/1165#discussion_r15147430
--- Diff:
core/src/main/scala/org/apache/spark/util/collection/SizeTracker.scala ---
@@ -0,0 +1,105 @@
+/*
+ * Licensed to the Apache Software
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1474#issuecomment-49536289
QA tests have started for PR 1474. This patch merges cleanly. brView
progress:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16861/consoleFull
---
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1443#issuecomment-49536333
Thanks - I can merge this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1474#issuecomment-49536330
QA results for PR 1474:br- This patch FAILED unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/1443
---
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/1364#issuecomment-49536424
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1364#issuecomment-49536483
QA tests have started for PR 1364. This patch DID NOT merge cleanly!
brView progress:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1364#issuecomment-49536491
QA results for PR 1364:br- This patch FAILED unit tests.brbrFor more
information see test
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1497#issuecomment-49536515
QA results for PR 1497:br- This patch PASSES unit tests.br- This patch
merges cleanlybr- This patch adds no public classesbrbrFor more
information see test
Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/1253#issuecomment-49536672
Hey @sryza - I did a straw poll offline discussing this with a few other
contributors. The consensus was that it might be better to have a `--conf` flag
with an `=`
73 matches
Mail list logo
