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-1339) Adding IInputPartition.Cache() for data downlad and cache
Date Thu, 14 Apr 2016 23:47:25 GMT

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

Markus Weimer commented on REEF-1339:
-------------------------------------

Yes, go ahead! Thanks for picking it up!

One question: How would the user of the API indicate where to cache in the memory hierarchy?
Will we have an {{enum}} for that? Also, we might want to allow some flexibility. For example,
a user might want to indicate that the data shall be cached at least on local HDD, but at
most on the SSD.

> Adding IInputPartition.Cache() for data downlad and cache
> ---------------------------------------------------------
>
>                 Key: REEF-1339
>                 URL: https://issues.apache.org/jira/browse/REEF-1339
>             Project: REEF
>          Issue Type: Task
>            Reporter: Julia
>              Labels: FT
>
> Currently, in FileSystemInputPartition, data downloading is implemented in Initilaize()
and called from GetPartitionHandle. It doesn't give client a flexibility to decide when to
download data. Besides, if client wants to cache data in advance, they need to call GetPartitionHandle()
and iterate the data. 
> We would like to expose a new API Cache() in IInputPartition which performs data download
to RAM, SSD, HDD, etc based on client's configuration. 
> The method should be called in ContextStartHandler  in IMRU scenarios. 



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

Mime
View raw message