[
https://issues.apache.org/jira/browse/SAMZA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Riccomini resolved SAMZA-353.
-----------------------------------
Resolution: Won't Fix
Resolving as won't fix for now. We can certainly revisit if more
multi-subscriber partition use-cases pop up.
>From the design doc, we have:
# Broadcast streams
# Global state
# Multi-subscriber partitions
For broadcast streams (1), we agreed to support task coordination for broadcast
streams through a non-Kafka control channel (RPC, TCP, etc).
For global state (2), I opened SAMZA-402 to solve the issue without the use of
an SSP grouper.
For multi-subscriber partitions (3), we have agreed not to support this for now.
> 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.3.4#6332)
