You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Kay Ousterhout (JIRA)" <ji...@apache.org> on 2016/06/17 19:15:06 UTC
[jira] [Resolved] (SPARK-15926) Improve readability of DAGScheduler
stage creation methods
[ https://issues.apache.org/jira/browse/SPARK-15926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kay Ousterhout resolved SPARK-15926.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.1.0
Fixed by https://github.com/apache/spark/pull/13677
> Improve readability of DAGScheduler stage creation methods
> ----------------------------------------------------------
>
> Key: SPARK-15926
> URL: https://issues.apache.org/jira/browse/SPARK-15926
> Project: Spark
> Issue Type: Sub-task
> Components: Scheduler
> Affects Versions: 2.0.0
> Reporter: Kay Ousterhout
> Assignee: Kay Ousterhout
> Priority: Minor
> Fix For: 2.1.0
>
>
> The current code to create new stages is very confusing: it's difficult to reason about which functions actually create new stages versus just looking up existing stages, and there are many similarly-named functions that do very different things. The goal of this JIRA is to clean some of that up.
--
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