You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Andrew Chung (JIRA)" <ji...@apache.org> on 2015/12/13 05:36:46 UTC

[jira] [Updated] (REEF-1075) Create Tasklet abstraction to enable one-to-many mapping of "Future-like" object to TaskletIds

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

Andrew Chung updated REEF-1075:
-------------------------------
    Summary: Create Tasklet abstraction to enable one-to-many mapping of "Future-like" object to TaskletIds  (was: Allow one-to-many mapping of "Future-like" object to TaskletIds)

> Create Tasklet abstraction to enable one-to-many mapping of "Future-like" object to TaskletIds
> ----------------------------------------------------------------------------------------------
>
>                 Key: REEF-1075
>                 URL: https://issues.apache.org/jira/browse/REEF-1075
>             Project: REEF
>          Issue Type: Task
>          Components: Vortex
>            Reporter: Andrew Chung
>            Assignee: Andrew Chung
>
> Currently, a {{VortexFuture}} is mapped to a single {{TaskletId}}. We need an abstraction to facilitate local aggregation such that a single "Future-like" object can map to many TaskletIds, such that the user will be informed of all the Function-Input pairs that are aggregated on local aggregations, instead of the single Function-Input pair that is represented by a {{VortexFuture}}.



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