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/04/07 17:00:41 UTC

[jira] [Updated] (SAMZA-89) Provide topics task is responsible for in InitableTask

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

Chris Riccomini updated SAMZA-89:
---------------------------------

    Fix Version/s:     (was: 0.7.0)

> Provide topics task is responsible for in InitableTask
> ------------------------------------------------------
>
>                 Key: SAMZA-89
>                 URL: https://issues.apache.org/jira/browse/SAMZA-89
>             Project: Samza
>          Issue Type: Improvement
>          Components: container
>    Affects Versions: 0.6.0
>            Reporter: Jakob Homan
>            Priority: Minor
>
> Right now tasks can determine what partition they're handling via the TaskContext.getPartition method and, with some work, what topics the entire job is responsible via the config that's passed into InitableTask as well.  But there's no easy way to figure out what topics a specific task is responsible for, particularly when dealing with a heterogeneous number of partitions per topic.  We should have a method on TaskContext that returns a set of the topics this task instance will be receiving messages for.
> Arguably, this method (and the accompanying getPartition) should be included in TaskCoordinator so that tasks don't have to implement InitableTask just to get this info (and in the event that in the future we have dynamic topics/partitions per task).



--
This message was sent by Atlassian JIRA
(v6.2#6252)