Github user ueshin commented on the pull request:
https://github.com/apache/spark/pull/12655#issuecomment-215317033
I saw the PR #8427 now.
Both the #8427 approach and @markhamstra's approach (should we use
`getOrElseUpdate` instead of `getOrElse`?) seem like the simplest way to fix
the duplicate-stage issue except a risk of `StackOverflowError`.
I agree that we should fix the duplicate-stage issue first in the simplest
way possible, by #8427 or @markhamstra's, and then discuss a risk of `SOE`
after one of them is merged.
---
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]
