[
https://issues.apache.org/jira/browse/SAMZA-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14128391#comment-14128391
]
Martin Kleppmann commented on SAMZA-402:
----------------------------------------
+1 on the proposal. I'm in favour of use case specific configuration (2), since
it's easier to use, and I can't see any benefit in the greater generality of a
more complex configuration.
Detail question: from which changelog partition(s) should a local shared store
be restored/updated? If several partitions are consumed, this introduces an
ordering problem. I am inclined to say that this stream should be created with
one partition, and if there are several partitions, the job only reads from
partition 0 and ignores the others. As shared local state is intended for
fairly small data volumes, it shouldn't be a problem to put it all in one
partition.
> 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)
