Github user kayousterhout commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-215240356
@markhamstra why is the newOrUsedShuffleStage approach better / different?
IMO the existing code is very convoluted at the moment, but we should first
fix the duplicate-stage bug (in the simplest way possible), and then in a
separate PR address cleaning up some of the function calls so this whole thing
is less convoluted and easier to reason about. But I realize I may be missing
some issue that the simple fix in #8923 doesn't address.
---
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]
