[ 
https://issues.apache.org/jira/browse/SAMZA-123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14062329#comment-14062329
 ] 

Martin Kleppmann commented on SAMZA-123:
----------------------------------------

The latest patch doesn't quite cleanly apply on master. Other than that, I am 
ok with committing this. There are some remaining issues, but we can address 
them in follow-on tickets:

* Backwards-compatibility or conversion of checkpoints (allow Samza 0.8 to read 
Samza 0.7 checkpoint)?
* CheckpointTool is broken and needs to be rewritten
* Update docs on the website to describe the new world order and new 
configuration properties
* If the same SSP is assigned to several TaskInstances, messages from that SSP 
should be delivered to all matching TaskInstances, not just one


> Move topic partition grouping to the AM and generalize
> ------------------------------------------------------
>
>                 Key: SAMZA-123
>                 URL: https://issues.apache.org/jira/browse/SAMZA-123
>             Project: Samza
>          Issue Type: Sub-task
>          Components: container
>    Affects Versions: 0.6.0
>            Reporter: Jakob Homan
>            Assignee: Jakob Homan
>             Fix For: 0.8.0
>
>         Attachments: SAMZA-123-2.patch, SAMZA-123-3.patch, SAMZA-123-4.patch, 
> SAMZA-123-5.patch, SAMZA-123-6.patch, SAMZA-123-7.patch, 
> SAMZA-123-design-doc.md, SAMZA-123-design-doc.pdf, SAMZA-123-draft.patch
>
>
> Currently the AM sends a set of all the topics and partitions to the 
> container, which then groups them by partition and assigns each set to a task 
> instance. By moving the grouping to the AM, we can assign arbitrary groups to 
> task instances, which will allow more partitioning strategies, as discussed 
> in SAMZA-71.



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

Reply via email to