Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/11986#issuecomment-202071373
It is not at all clear to me from either this PR or your insufficient JIRA
why you think it is valid to ignore all of the cache logic in the
MapOutputTracker and
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/11986#issuecomment-202057975
Can you connect this to your JIRA please?
And explain why this change is OK. I'm not familiar myself with this bit of
the code so not sure if it's always valid to
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/11986#issuecomment-202028352
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/11986#issuecomment-202028356
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11986#issuecomment-202027911
**[Test build #54285 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54285/consoleFull)**
for PR 11986 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/11986#issuecomment-202008756
**[Test build #54285 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54285/consoleFull)**
for PR 11986 at commit
GitHub user witgo opened a pull request:
https://github.com/apache/spark/pull/11986
DAGScheduler should get map output statuses directly.
## What changes were proposed in this pull request?
Add a new method to `MapOutputTracker` class
```scala
def
