[
https://issues.apache.org/jira/browse/SAMZA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14109708#comment-14109708
]
Chinmay Soman commented on SAMZA-353:
-------------------------------------
One last comment about broadcast stream:
====================================
If we plan to use this for coordination amongst the tasks, I personally think
we might be better off defining a separate control channel for Samza. This can
be coordinated via the AM (which can be reading the coordination messages from
an input Kafka stream). This of course assumes that we have AM -> container
communication channel which itself isn't finalized.
If its not for coordination, then everything else can be driven by the global
state store (which can be implemented in other simpler ways - as you have
described at the end of that design).
> 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
> 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.2#6252)
