[
https://issues.apache.org/jira/browse/SAMZA-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14164006#comment-14164006
]
Chris Riccomini commented on SAMZA-424:
---------------------------------------
In the "composition via code" implementation, it seems like a bit of a misfit
that every InitableTask.init method will create a storage engine, even if
isShared is set to true. In this case, what will happen to the other storage
engines? They'll presumably need to be shut down, and not used. I suppose the
framework can do this, but it seems a bit off to create a bunch of objects and
not use them. Not a blocker, though.
I think that I'm +1 on the "composition via code" approach. I think this change
would be in keeping with moving towards a
[TopologyBuilder|http://storm.apache.org/apidocs/backtype/storm/topology/TopologyBuilder.html]
style pattern for wiring up Samza jobs, if that's a direction that we go in
(as mentioned
[here|http://mail-archives.apache.org/mod_mbox/samza-dev/201409.mbox/%3ccakow62ney6f7qqabcwgdcpmeu4jwx74xzov_0-gi6myjrpc...@mail.gmail.com%3E]).
This is a pretty big change to the API, though. [~martinkl], [~jkreps],
[~theduderog], [~closeuris], do you guys care to comment?
> 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)
