[
https://issues.apache.org/jira/browse/SAMZA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14125740#comment-14125740
]
Chris Riccomini commented on SAMZA-402:
---------------------------------------
bq. Any caching that is put in place isn't really specific to Samza in any way.
So I am inclined to think that Samza doesn't need explicit support for calls to
external DBs — people can just use whatever existing mechanisms there are. Or
am I missing something?
I agree Samza doesn't need to provide any direct support for caching. One thing
we're discussing implementing is a ReadThroughCache store. The reason for
implementing the cache as a store is that you can use it as a warm cache when
the job is restarted if you were to attach a changelog to it. Implementing this
cache shouldn't change Samza at all, but it'd be nice for users to have
something to use in cases where they are going to query a remote store.
> Provide a "shared state" store among StreamTasks
> ------------------------------------------------
>
> Key: SAMZA-402
> URL: https://issues.apache.org/jira/browse/SAMZA-402
> Project: Samza
> Issue Type: Bug
> Components: container, kv
> Affects Versions: 0.8.0
> Reporter: Chris Riccomini
> Attachments: DESIGN-SAMZA-402-0.md, DESIGN-SAMZA-402-0.pdf
>
>
> There has been a lot of discussion about shared state stores in SAMZA-353.
> Initially, it seemed as though we might implement them through SAMZA-353, but
> now it seems more preferable to implement them separately. As such, this
> ticket is to discuss global state/shared state (terms that are being used
> interchangeably) between StreamTasks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
