You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chinmay Soman (JIRA)" <ji...@apache.org> on 2014/10/08 20:40:34 UTC

[jira] [Updated] (SAMZA-424) Add a Cache state API to the Samza container

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

Chinmay Soman updated SAMZA-424:
--------------------------------
    Attachment: samza-424-cache-api_1.pdf
                SAMZA-424-Cache-API_1.md

Re-worked the design based on the comments from (and discussion with) [~criccomini]

Please have a look

> Add a Cache state API to the Samza container
> --------------------------------------------
>
>                 Key: SAMZA-424
>                 URL: https://issues.apache.org/jira/browse/SAMZA-424
>             Project: Samza
>          Issue Type: New Feature
>          Components: container
>            Reporter: Chinmay Soman
>            Assignee: Chinmay Soman
>         Attachments: SAMZA-424-Cache-API_0.pdf, SAMZA-424-Cache-API_1.md, samza-424-cache-api_1.pdf
>
>
> There are cases when the user code needs access to a 'cache' which can be used to store custom data. This cache is different from the KeyValue store in the following ways:
> * At the very least Needs to support LRU (Least Recently Used) and TTL (Time To Live) eviction strategies
> * May not support all() and range() operations (since this wreaks havoc with the eviction operation)
> * Needs to exist at a per task or a per container level.



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