reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1357) Allow different caching levels for caching in IInputPartition
Date Fri, 24 Jun 2016 15:44:16 GMT

    [ https://issues.apache.org/jira/browse/REEF-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348448#comment-15348448
] 

Markus Weimer commented on REEF-1357:
-------------------------------------

We could use a {{class MapInputPartition : Name<IInputPartition>}} to identify the object
to be injected to the Map task. We would then bind a caching implementation to that name,
which in turn receives the actual {{IInputPartition}} as a constructor parameter. We don't
need a public {{Cache()}} method if we perform the caching during first access.

> Allow different caching levels for caching in IInputPartition
> -------------------------------------------------------------
>
>                 Key: REEF-1357
>                 URL: https://issues.apache.org/jira/browse/REEF-1357
>             Project: REEF
>          Issue Type: Improvement
>          Components: IMRU, REEF.NET
>            Reporter: Andrew Chung
>            Assignee: Andrew Chung
>              Labels: FT
>
> Caching in {{IInputPartition}} is currently entirely dependent on the implementation
of the {{IInputPartition}}. We should modify/expand {{IInputPartition}} such that the data
loading component is fully separate from the caching component. An idea is to instead provide
only a single concrete {{IInputPartition}} implementation (while deprecating the old implementations)
and use the composition model, complete with an {{IDataLoader}} which fetches data back in
a {{Stream}}, and an {{IDataCache}}, which allows caching at granular levels.



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

Mime
View raw message