[
https://issues.apache.org/jira/browse/SPARK-4655?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen resolved SPARK-4655.
------------------------------
Resolution: Fixed
Fix Version/s: 1.4.0
Issue resolved by pull request 4708
[https://github.com/apache/spark/pull/4708]
> 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: Ilya Ganelin
> Fix For: 1.4.0
>
>
> 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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
