Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/17166
The task killed messages should be informative, and I don't think we should
sacrifice informative messages just so they can be shown concisely in the stage
summary view. I think it's much
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/17166
Drilling down into the detail view is kind of cumbersome -- I think it's
most useful to have a good summary at the progress bar, and then the user can
refer to logs for detailed per-task debugging.
Github user ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/15363#discussion_r106088842
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -51,6 +51,11 @@ case class
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17299
---
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 ueshin commented on the issue:
https://github.com/apache/spark/pull/17299
Thanks! Merging to 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 this feature
enabled and
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17186
**[Test build #74581 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74581/testReport)**
for PR 17186 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/17166
Why not just just "X killed" in the stage summary? It seems like overkill
to put the reasons for all of the killings there, now that I'm seeing the
screenshot, since they're already in the
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/15363#discussion_r106086454
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -51,6 +51,11 @@ case class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15945
**[Test build #74580 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74580/testReport)**
for PR 15945 at commit
Github user ron8hu commented on a diff in the pull request:
https://github.com/apache/spark/pull/15363#discussion_r106084556
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -51,6 +51,11 @@ case class
Github user yanboliang commented on a diff in the pull request:
https://github.com/apache/spark/pull/17274#discussion_r106083228
--- Diff: R/pkg/inst/tests/testthat/test_context.R ---
@@ -177,6 +177,13 @@ test_that("add and get file to be downloaded with
Spark job on every node",
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17299
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74578/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17299
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17299
**[Test build #74578 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74578/testReport)**
for PR 17299 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17166
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74576/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17166
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17166
**[Test build #74576 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74576/testReport)**
for PR 17166 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15009
**[Test build #74579 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74579/testReport)**
for PR 15009 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15945
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15945
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74577/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15945
**[Test build #74577 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74577/testReport)**
for PR 15945 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15604
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74575/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15604
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15604
**[Test build #74575 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74575/testReport)**
for PR 15604 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17166
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74572/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17166
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17166
**[Test build #74572 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74572/testReport)**
for PR 17166 at commit
Github user kishorvpatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/15009#discussion_r106080005
--- Diff:
resource-managers/yarn/src/test/scala/org/apache/spark/deploy/yarn/YarnClusterSuite.scala
---
@@ -252,20 +307,55 @@ class YarnClusterSuite
Github user viirya commented on the issue:
https://github.com/apache/spark/pull/17267
LGTM cc @davies @holdenk
---
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
Github user ueshin commented on the issue:
https://github.com/apache/spark/pull/17299
LGTM, thank you for your follow-up!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17297
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17297
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74566/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17297
**[Test build #74566 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74566/testReport)**
for PR 17297 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17300
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 project does not have this
GitHub user ConeyLiu opened a pull request:
https://github.com/apache/spark/pull/17300
[SPARK-19956][Core]Optimize a location order of blocks with topology
information
## What changes were proposed in this pull request?
When call the method getLocations of BlockManager, we
Github user uncleGen commented on the issue:
https://github.com/apache/spark/pull/17267
ping @viirya
---
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
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17166
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17166
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74570/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17166
**[Test build #74570 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74570/testReport)**
for PR 17166 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17232
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17232
thanks, merging to 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 this feature
enabled and
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17178
---
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 felixcheung commented on the issue:
https://github.com/apache/spark/pull/17178
thanks!
merged to 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 this feature
enabled
Github user lw-lin commented on the issue:
https://github.com/apache/spark/pull/17268
Thank you @marmbrus for the detailed explanation!
> For that reason, I think its safest to require the user to explicitly
include the timestamp.
Yea, let me update this in this
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15125
@jkbradley @ankurdave would you like to review?
---
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 issue:
https://github.com/apache/spark/pull/17297
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17297
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74562/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17297
**[Test build #74562 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74562/testReport)**
for PR 17297 at commit
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17251
@cloud-fan . Sorry, but could you review this `stack` PR once again? :)
---
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 ioana-delaney commented on a diff in the pull request:
https://github.com/apache/spark/pull/15363#discussion_r106074890
--- Diff:
sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/optimizer/CostBasedJoinReorder.scala
---
@@ -51,6 +51,11 @@ case class
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17266
For non-error message cases, incorrect result is also a problem in this
issue.
---
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 jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/17241
ping @hvanhovell @gatorsmile
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17232
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74574/
Test PASSed.
---
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17266
The following is the error message. Since we are not escaping in the spark
master, the behavior (incorrect filtering or the error message) is the same
from the master branch Spark.
```
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17232
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17232
**[Test build #74574 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74574/testReport)**
for PR 17232 at commit
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/17255
---
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/17277
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17255
thanks, merging to 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 this feature
enabled and
Github user cloud-fan commented on a diff in the pull request:
https://github.com/apache/spark/pull/17255#discussion_r106072933
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/datasources/json/JsonInferSchema.scala
---
@@ -40,18 +40,11 @@ private[sql] object
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17232
LGTM
---
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
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17299
LGTM
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17299
**[Test build #74578 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74578/testReport)**
for PR 17299 at commit
Github user lw-lin commented on the issue:
https://github.com/apache/spark/pull/17299
This is the fix for the streaming counter-part (i.e. Structured Streaming),
@ueshin @gatorsmile would you take a look? Thanks!
---
If your project is set up for it, you can reply to this email and
GitHub user lw-lin opened a pull request:
https://github.com/apache/spark/pull/17299
[SPARK-19817][SS] Make it clear that `timeZone` is a general option in
DataStreamReader/Writer
## What changes were proposed in this pull request?
As timezone setting can also affect
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17298
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74568/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17298
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 project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17164
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17298
**[Test build #74568 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74568/testReport)**
for PR 17298 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/17164
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74569/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17164
**[Test build #74569 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74569/testReport)**
for PR 17164 at commit
Github user VinceShieh commented on the issue:
https://github.com/apache/spark/pull/17237
Sure. No problem!
---
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
Github user dongjoon-hyun closed the pull request at:
https://github.com/apache/spark/pull/17223
---
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
Github user dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17223
I'll close this PR and JIRA issue.
---
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 dongjoon-hyun commented on the issue:
https://github.com/apache/spark/pull/17223
I see. That's the reason why not to support that. Thank you, @cloud-fan.
---
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 cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17266
can we say something more in the error message? We should explain that it's
a hive bug.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15945
**[Test build #74577 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74577/testReport)**
for PR 15945 at commit
Github user sitalkedia commented on the issue:
https://github.com/apache/spark/pull/12436
@jisookim0513 - created a new PR -
https://github.com/apache/spark/pull/17297
---
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 SparkQA commented on the issue:
https://github.com/apache/spark/pull/17166
**[Test build #74576 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74576/testReport)**
for PR 17166 at commit
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/17177
@ep1804 @jbax Thank you. I will cc and inform you both when I happen to see
a PR bumping up the version to 2.4.0 (or probably I guess I will).
---
If your project is set up for it, you can
Github user ep1804 closed the pull request at:
https://github.com/apache/spark/pull/17177
---
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 ep1804 commented on the issue:
https://github.com/apache/spark/pull/17177
I agree with you @HyukjinKwon , this PR will be closed for now and re-open.
And, thank you for the notice @jbox !
---
If your project is set up for it, you can reply to this email and have
Github user ericl commented on a diff in the pull request:
https://github.com/apache/spark/pull/17166#discussion_r106066177
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -710,7 +710,11 @@ private[spark] class TaskSetManager(
Github user windpiger commented on a diff in the pull request:
https://github.com/apache/spark/pull/17287#discussion_r106065119
--- Diff:
sql/catalyst/src/test/scala/org/apache/spark/sql/catalyst/catalog/SessionCatalogSuite.scala
---
@@ -76,468 +118,499 @@ class
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15604
**[Test build #74575 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74575/testReport)**
for PR 15604 at commit
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/15604
@erenavsarogullari please file a JIRA when you see test failures instead of
ignoring them. I updated https://issues.apache.org/jira/browse/SPARK-19803 for
the first failure, but please file
Github user kayousterhout commented on the issue:
https://github.com/apache/spark/pull/15604
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 this feature
enabled
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15945
**[Test build #74573 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74573/testReport)**
for PR 15945 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15945
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74573/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15945
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17232
**[Test build #74574 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74574/testReport)**
for PR 17232 at commit
Github user cloud-fan commented on the issue:
https://github.com/apache/spark/pull/17223
Since hive client is shared among all sessions, we can't set hive conf
dynamically, to keep session isolation. I think we should treat hive conf as
static sql conf, and throw exception when users
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15945
**[Test build #74573 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74573/testReport)**
for PR 15945 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15945
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15945
**[Test build #74571 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74571/testReport)**
for PR 15945 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15945
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/74571/
Test FAILed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/17166
**[Test build #74572 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/74572/testReport)**
for PR 17166 at commit
Github user jerryshao commented on the issue:
https://github.com/apache/spark/pull/16788
>Trying to put it differently: if Spark had its own, secure method for
distributing the initial set of delegation tokens needed by the executors (+ AM
in case of YARN), then the YARN backend
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/17166#discussion_r106063119
--- Diff:
core/src/main/scala/org/apache/spark/scheduler/TaskSetManager.scala ---
@@ -710,7 +710,11 @@ private[spark] class TaskSetManager(
Github user kayousterhout commented on a diff in the pull request:
https://github.com/apache/spark/pull/17166#discussion_r106063061
--- Diff: core/src/main/scala/org/apache/spark/executor/Executor.scala ---
@@ -239,8 +244,9 @@ private[spark] class Executor(
*/
1 - 100 of 656 matches
Mail list logo
