Github user JoshRosen commented on the issue:
https://github.com/apache/spark/pull/16250
I agree with above comments and would be +1 to not performing further
review on this set of cosmetic changes. The reason why the DAGScheduler is
complicated isn't due to surface-level code issues but due to design complexity
and just putting a fresh coat of paint on it via small-scale changes eats up
reviewer time, makes it harder to backport fixes without merge conflicts, makes
it harder to hunt for regressions since there are more diffs to bisect, etc.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
