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 2014/11/29 20:46:12 UTC

[jira] [Created] (SPARK-4655) Split Stage into ShuffleMapStage and ResultStage subclasses

Josh Rosen created SPARK-4655:
---------------------------------

             Summary: Split Stage into ShuffleMapStage and ResultStage subclasses
                 Key: SPARK-4655
                 URL: https://issues.apache.org/jira/browse/SPARK-4655
             Project: Spark
          Issue Type: Sub-task
          Components: Spark Core
            Reporter: Josh Rosen
            Assignee: Josh Rosen


The scheduler's {{Stage}} class has many fields which are only applicable to result stages or shuffle map stages.  As a result, I think that it makes sense to make {{Stage}} into an abstract base class with two subclasses, {{ResultStage}} and {{ShuffleMapStage}}.  This would improve the understandability of the DAGScheduler code. 



--
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