[
https://issues.apache.org/jira/browse/SAMZA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Riccomini updated SAMZA-402:
----------------------------------
Attachment: DESIGN-SAMZA-402-1.pdf
DESIGN-SAMZA-402-1.md
Attaching updated design docs. Sorry, it got a bit bigger.
* Called out difference between unpartitioned local state and remote external
state.
* Atomicity, handling deletions, message mutation, inter-task state, and
lagging state sections are largely unchanged.
* Added a "proposed solutions" section to propose a an external read-through
cache.
* Updated implementation section to think through the high-level design
required to unify the existing partition state implementation in Samza with
external read-through cache and unpartitioned local state. The goal is to
re-use and generalize as much of what we already have as possible.
> 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,
> DESIGN-SAMZA-402-1.md, DESIGN-SAMZA-402-1.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)
