spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Rosen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-3902) Stabilize AsyncRDDActions and expose its methods in Java API
Date Mon, 20 Oct 2014 03:03:33 GMT

     [ https://issues.apache.org/jira/browse/SPARK-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Rosen resolved SPARK-3902.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.2.0

Issue resolved by pull request 2760
[https://github.com/apache/spark/pull/2760]

> Stabilize AsyncRDDActions and expose its methods in Java API
> ------------------------------------------------------------
>
>                 Key: SPARK-3902
>                 URL: https://issues.apache.org/jira/browse/SPARK-3902
>             Project: Spark
>          Issue Type: New Feature
>          Components: Java API, Spark Core
>            Reporter: Josh Rosen
>            Assignee: Josh Rosen
>             Fix For: 1.2.0
>
>
> The AsyncRDDActions methods are currently the easiest way to determine Spark jobs' ids
for use in progress-monitoring code (see SPARK-2636).  AsyncRDDActions is currently marked
as {{@Experimental}}; for 1.2, I think that we should stabilize this API and expose it in
Java, too.
> One concern is whether there's a better async API design that we should prefer over this
one as our stable API; I had some ideas for a more general API in SPARK-3626 (discussed in
much greater detail on GitHub: https://github.com/apache/spark/pull/2482) but decided against
the more general API due to its confusing cancellation semantics.  Given this, I'd be comfortable
stabilizing our current API.



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


Mime
View raw message