You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2015/05/24 00:01:17 UTC

[jira] [Commented] (SPARK-4653) DAGScheduler refactoring and cleanup

    [ https://issues.apache.org/jira/browse/SPARK-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14557544#comment-14557544 ] 

Josh Rosen commented on SPARK-4653:
-----------------------------------

Before we begin code-changing refactorings, I would be in favor of a series of patches which heavily-comments the existing code.  I suspect that trying to reverse-engineer a design document for the current DAGScheduler will expose many corner-cases / bugs and will help us to distinguish between inherent and accidental complexity.

> DAGScheduler refactoring and cleanup
> ------------------------------------
>
>                 Key: SPARK-4653
>                 URL: https://issues.apache.org/jira/browse/SPARK-4653
>             Project: Spark
>          Issue Type: Improvement
>          Components: Scheduler
>            Reporter: Josh Rosen
>            Assignee: Josh Rosen
>
> This is an umbrella JIRA for DAGScheduler refactoring and cleanup.  Please comment or open sub-issues if you have refactoring suggestions that should fall under this umbrella.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org