[
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-0.md
DESIGN-SAMZA-402-0.pdf
Attaching initial design doc.
The question at hand is whether the current approach is sufficient for us to
proceed with an implementation?
I'm leaning towards "no" at the moment. I feel as though the lack of atomicity,
deletion support, and lagging state make this current design pretty difficult
to use properly under most use cases.
It seems as though using a cache in front of a remote DB is a much easier way
to handle the read-only cache use case. I'm not quite sure what to do about the
inter-task state use case, specifically as it relates to lagging state.
> 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)
