[
https://issues.apache.org/jira/browse/SAMZA-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14548569#comment-14548569
]
Yi Pan (Data Infrastructure) commented on SAMZA-676:
----------------------------------------------------
{quote}
This does not break the register part, but breaks the poll() part as I
mentioned because we can only return A Map with SSP->List<msg> mapping. Not
sure how we can return a Map where one SSP have two different lists of msgs -
the broadcast stream has two offsets and so the msgs from it are different.
{quote}
Yes, that is the problem. How about that we add MulticastSystemConsumer as an
extended SystemConsumer interface as well and instantiate this SystemConsumer
class if the user configured to use broadcast topic? This may not be too bad
since SystemConsumer is an interface to the underlying messaging systems and
the systems do not support this can choose not to implement this additional
interface.
> Implement Broadcast Stream
> --------------------------
>
> Key: SAMZA-676
> URL: https://issues.apache.org/jira/browse/SAMZA-676
> Project: Samza
> Issue Type: Improvement
> Components: container
> Reporter: Yan Fang
> Assignee: Yan Fang
> Attachments: BroadcastStreamDesign.md, BroadcastStreamDesign.pdf
>
>
> There are a lot of discussion in SAMZA-353 about assigning the same SSP to
> multiple taskNames. This ticket is a subset of the discussion. Only focus on
> the broadcast stream implementation.
> The goal is to assign one SSP to all the taskNames.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
