Github user markhamstra commented on the pull request:
https://github.com/apache/spark/pull/5396#issuecomment-90717805
Ok, in looking further, I see that I'm going to have a more general problem
with this PR. I can't see exposing carefully nested and scoped portions of
functions to the rest of the DAGScheduler as a good thing. Things are defined
and visible where they make sense and are needed, and are intentionally not
available elsewhere. To me, exposing additional interfaces to all of the
DAGScheduler makes it more complicated to figure out how and when the various
pieces should be used, not less.
---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
