[
https://issues.apache.org/jira/browse/SAMZA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221535#comment-14221535
]
Chris Riccomini commented on SAMZA-353:
---------------------------------------
bq. Another way of looking at this is that it allows scatter-gather-type data
flows.
This is a pretty compelling use case.
bq. Global state (SAMZA-402) doesn't really do what we need
As I understand it, if the query set is reasonably small, you could use global
state and store all queries everywhere. As you said, this means you're
bottle-necked on scale-out of the queries, though. The same holds true for
documents, though I imagine that the documents are likely to be larger. In any
case, I take your point. What's ideal is something that scales out both for
arbitrary sized queries and arbitrary sized documents.
> Support assigning the same SSP to multiple tasknames
> ----------------------------------------------------
>
> Key: SAMZA-353
> URL: https://issues.apache.org/jira/browse/SAMZA-353
> Project: Samza
> Issue Type: Bug
> Components: container
> Affects Versions: 0.8.0
> Reporter: Jakob Homan
> Labels: design
> Fix For: 0.9.0
>
> Attachments: DESIGN-SAMZA-353-0.md, DESIGN-SAMZA-353-0.pdf
>
>
> Post SAMZA-123, it is possible to add the same SSP to multiple tasknames,
> although currently we check for this and error out if this is done. We
> should think through the implications of having the same SSP appear in
> multiple tasknames and support this if it makes sense.
> This could be used as a broadcast stream that's either added by Samza itself
> to each taskname, or individual groupers could do this as makes sense. Right
> now the container maintains a map of SSP to TaskInstance and delivers the ssp
> to that task instance. With this change, we'd need to change the map to SSP
> to Set[TaskInstance] and deliver the message to each TI in the set.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
