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/09/30 00:11:33 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14152387#comment-14152387 ]
Chinmay Soman commented on SAMZA-424:
-------------------------------------
The design is up for review. 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
>
>
> 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)