You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/09/11 19:26:35 UTC

[jira] [Updated] (SAMZA-353) Support assigning the same SSP to multiple tasknames

     [ https://issues.apache.org/jira/browse/SAMZA-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Riccomini updated SAMZA-353:
----------------------------------
    Labels: design  (was: )

> 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
>         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)