Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/7098#issuecomment-116876134
Thanks - merged 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 marmbrus commented on the pull request:
https://github.com/apache/spark/pull/6874#issuecomment-116877713
Do we also need to add this to `functions.py`?
---
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/7100#issuecomment-116877668
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7099#issuecomment-116877667
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/7100#issuecomment-116877652
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/7103#issuecomment-116878312
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 davies commented on a diff in the pull request:
https://github.com/apache/spark/pull/6444#discussion_r33526988
--- Diff:
sql/catalyst/src/main/java/org/apache/spark/sql/execution/UnsafeExternalRowSorter.java
---
@@ -0,0 +1,171 @@
+/*
+ * Licensed to the Apache
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7100#issuecomment-116879983
Merged build finished. Test 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7100#issuecomment-116879930
[Test build #36049 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36049/console)
for PR 7100 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7100#issuecomment-116880315
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/6981#issuecomment-116880347
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7100#issuecomment-116880343
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6981#issuecomment-116880325
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 feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/7084#discussion_r33527772
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/CountVectorizer.scala ---
@@ -0,0 +1,80 @@
+/*
+ * Licensed to the Apache Software
Github user ankurcha commented on the pull request:
https://github.com/apache/spark/pull/5563#issuecomment-116881510
* Looking at the way this feature is being used (as per marathon) and the
age of the commits to the concerned attributes.cpp and values.cpp files, the
feature is
Github user PraveenSeluka commented on the pull request:
https://github.com/apache/spark/pull/5233#issuecomment-116881567
@sryza - After the fix on YARN side, I have not seen this issue - We can
close this (and also the JIRA).
---
If your project is set up for it, you can reply to
Github user tarekauel commented on a diff in the pull request:
https://github.com/apache/spark/pull/6981#discussion_r33527804
--- Diff: python/pyspark/sql/functions.py ---
@@ -487,6 +487,114 @@ def ntile(n):
return Column(sc._jvm.functions.ntile(int(n)))
Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/7048#issuecomment-116881471
This LGTM, pending Jenkins build result.
---
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 feynmanliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/7084#discussion_r33528713
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/CountVectorizer.scala ---
@@ -0,0 +1,80 @@
+/*
+ * Licensed to the Apache Software
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7058#issuecomment-116884823
A slightly related concern is mutation of non-default arguments. There
might be cases where we need to defensively copy the input arguments, but I'm
not familiar
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/6413#issuecomment-116884814
@yhuai sorry it's a big change. :) can you review this for me?
---
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/7036
---
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 aray commented on a diff in the pull request:
https://github.com/apache/spark/pull/7104#discussion_r33529689
--- Diff:
graphx/src/main/scala/org/apache/spark/graphx/PartitionStrategy.scala ---
@@ -32,7 +32,7 @@ trait PartitionStrategy extends Serializable {
object
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7027
---
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/7101#issuecomment-116885992
Merged build finished. Test 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/7104#issuecomment-116885979
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/7103#issuecomment-116893870
[Test build #36059 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36059/console)
for PR 7103 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7103#issuecomment-116893875
Merged build finished. Test FAILed.
---
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 shivaram commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-116893862
cc @andrewor14 who probably knows some thing about the YARN tests
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7101#issuecomment-116895578
[Test build #36061 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36061/console)
for PR 7101 at commit
Github user dbtsai commented on a diff in the pull request:
https://github.com/apache/spark/pull/7080#discussion_r33532011
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/classification/LogisticRegression.scala
---
@@ -534,27 +554,39 @@ private class LogisticCostFun(
Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/7035#issuecomment-116896114
Can you wait a little bit for #7034? Hopefully it will be simpler once
#7034 merged.
---
If your project is set up for it, you can reply to this email and have
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6662#issuecomment-116896184
I have updated the description on the JIRA. However, this patch is
definitely not the correct fix. The user should be able to call
`sc.requestExecutors` (a public
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6960#issuecomment-116908089
LGTM merging into master
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7048#issuecomment-116909872
[Test build #36052 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36052/console)
for PR 7048 at commit
Github user rekhajoshm commented on the pull request:
https://github.com/apache/spark/pull/6973#issuecomment-116913875
thanks @andrewor14 for your quick input.the last commit 2ce5760 was updated
for the comment from @srowen kindly check.thanks
---
If your project is set up for it,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6394#issuecomment-116913961
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/6394#issuecomment-116913976
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7107#issuecomment-116915401
Merged build finished. Test FAILed.
---
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/7107#issuecomment-116915343
[Test build #36067 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36067/console)
for PR 7107 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6894#issuecomment-116914837
Would you mind making that small update (also to trigger tests again)?
Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6982#issuecomment-11694
[Test build #36073 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36073/consoleFull)
for PR 6982 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6982#issuecomment-116921630
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/7108#issuecomment-116921620
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/7101#issuecomment-116922432
[Test build #980 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/980/consoleFull)
for PR 7101 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6982#issuecomment-116921687
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
Github user rxin commented on a diff in the pull request:
https://github.com/apache/spark/pull/6853#discussion_r33536357
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/CheckAnalysis.scala
---
@@ -121,6 +122,17 @@ trait CheckAnalysis {
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/6743#discussion_r33536903
--- Diff: core/src/main/scala/org/apache/spark/api/r/RUtils.scala ---
@@ -0,0 +1,44 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF)
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7109#issuecomment-116930002
[Test build #36076 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36076/consoleFull)
for PR 7109 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7110#issuecomment-116935000
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
Github user sryza commented on the pull request:
https://github.com/apache/spark/pull/5233#issuecomment-116877465
There's no bug on the Spark side. @PraveenSeluka is this still something
you're running into? If this is causing pain to a lot of users it could be
worth the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7099#issuecomment-116877654
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 marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/6874#discussion_r33525785
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/functions.scala ---
@@ -747,9 +747,7 @@ object functions {
*/
@scala.annotation.varargs
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7094
---
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/7103#issuecomment-116878335
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6205#issuecomment-116878577
Merged build finished. Test 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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6981#issuecomment-116880728
[Test build #36054 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36054/consoleFull)
for PR 6981 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7100#issuecomment-116880727
[Test build #36053 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36053/consoleFull)
for PR 7100 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7051#issuecomment-116883795
Update: I don't think we should change the default behavior without better
understanding of how this feature works. The first step would be to write tests
and update
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7089#issuecomment-116886558
OK, merging into master 1.4, thanks @brkyvz. Do we need a fix for 1.3 as
well?
---
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/7031#issuecomment-116888365
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7055#issuecomment-116888345
Hm, I'm pretty confused. @litao-buptsse Which is your proposed fix, this
one or #7053? Did you intend to have different fixes merged into different
branches?
---
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7031#issuecomment-116888348
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/7097#issuecomment-116892032
Merged build finished. Test FAILed.
---
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/7097#issuecomment-116892028
[Test build #36058 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36058/console)
for PR 7097 at commit
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6992#issuecomment-116908613
@yanboliang Could you please make a JIRA and PR for updating the user guide
with the Python API? Thanks!
---
If your project is set up for it, you can reply to this
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6960
---
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 navis commented on a diff in the pull request:
https://github.com/apache/spark/pull/6810#discussion_r33533643
--- Diff:
sql/core/src/test/scala/org/apache/spark/sql/execution/AggregateSuite.scala ---
@@ -0,0 +1,59 @@
+/*
+ * Licensed to the Apache Software
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6983#issuecomment-116910464
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/6983#issuecomment-116910475
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6983#issuecomment-116910563
[Test build #36064 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36064/consoleFull)
for PR 6983 at commit
Github user jerryshao commented on the pull request:
https://github.com/apache/spark/pull/6870#issuecomment-116917074
I think the original blacklist mechanism and what @davies did is to avoid
the resubmitted tasks running on the same executors/hosts, which means tasks
should be
Github user jkbradley commented on a diff in the pull request:
https://github.com/apache/spark/pull/6039#discussion_r33536321
--- Diff:
mllib/src/main/scala/org/apache/spark/ml/feature/MinMaxScaler.scala ---
@@ -0,0 +1,166 @@
+/*
+ * Licensed to the Apache Software
Github user SaintBacchus commented on a diff in the pull request:
https://github.com/apache/spark/pull/7069#discussion_r33536245
--- Diff: core/src/main/scala/org/apache/spark/deploy/SparkHadoopUtil.scala
---
@@ -334,6 +334,17 @@ class SparkHadoopUtil extends Logging {
*
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7069#issuecomment-116924975
[Test build #36074 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36074/consoleFull)
for PR 7069 at commit
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6817#issuecomment-116924889
Also, echoing @squito's comments, I also don't really see why a new
`TaskResubmit` event is necessary. If a task is resubmitted, a new
`SparkListenerTaskStart` event
Github user jkbradley commented on the pull request:
https://github.com/apache/spark/pull/6039#issuecomment-116927872
@hhbyyh Thanks for the updates. It looks fine, except for 1 to-do: Can you
please add a note in the Scala doc, saying that this transformer does not yet
set the
Github user brkyvz commented on a diff in the pull request:
https://github.com/apache/spark/pull/6782#discussion_r33526888
--- Diff: sql/core/src/main/scala/org/apache/spark/sql/functions.scala ---
@@ -946,6 +947,38 @@ object functions {
def cosh(columnName: String): Column
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6981#issuecomment-116882775
[Test build #36054 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36054/console)
for PR 6981 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6981#issuecomment-116882815
Merged build finished. Test FAILed.
---
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 davies commented on the pull request:
https://github.com/apache/spark/pull/6981#issuecomment-116884298
In order to having this fast path, you should check it first, for example:
```
year = days / 365.24
day_in_year = days - year.toInt * 365.24
if
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116885235
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116885208
retest this please. SparkSubmitSuite --jars is really flaky...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7077#issuecomment-116885225
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/7031#issuecomment-116886922
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/7031#issuecomment-116886948
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/7089
---
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/7101#issuecomment-116894134
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7101#issuecomment-116894125
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 davies commented on the pull request:
https://github.com/apache/spark/pull/6743#issuecomment-116894129
@sun-rui Yes
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/7101#issuecomment-116895188
[Test build #36061 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/36061/consoleFull)
for PR 7101 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7101#issuecomment-116895581
Merged build finished. Test FAILed.
---
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/7101#issuecomment-116896777
Merged build finished. Test FAILed.
---
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 liancheng opened a pull request:
https://github.com/apache/spark/pull/7105
[SPARK-8720] [CORE] [HOTFIX] Escapes `/*' in the comment
The `/*` in the comment starts another unclosed comment block.
You can merge this pull request into a Git repository by running:
$
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/7031#issuecomment-116909354
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 SaintBacchus closed the pull request at:
https://github.com/apache/spark/pull/6662
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/7008#issuecomment-116910937
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6983#issuecomment-116912757
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
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/7107
[SPARK-8119] HeartbeatReceiver should replace executors, not kill
**Symptom.** If an executor in an application times out,
`HeartbeatReceiver` attempts to kill it. After this happens, however,
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6983#issuecomment-116912751
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
901 - 1000 of 1332 matches
Mail list logo
