You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "József Márton Jung (JIRA)" <ji...@apache.org> on 2015/07/08 15:08:04 UTC

[jira] [Updated] (SAMZA-682) Refactor Coordinator stream messages

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

József Márton Jung updated SAMZA-682:
-------------------------------------
    Attachment: SAMZA-682.0-based_on_SAMZA-670.patch

Attached [^SAMZA-682.0-based_on_SAMZA-670.patch]. This patch is based on SAMZA-670 branch, because the refactoring shares a lot of code which was changed in SAMZA-670. This is why there is no RB review request yet.

I think this ticket should be resolved after SAMZA-670 is done.

> Refactor Coordinator stream messages
> ------------------------------------
>
>                 Key: SAMZA-682
>                 URL: https://issues.apache.org/jira/browse/SAMZA-682
>             Project: Samza
>          Issue Type: Sub-task
>            Reporter: Naveen Somasundaram
>            Assignee: József Márton Jung
>             Fix For: 0.10.0
>
>         Attachments: SAMZA-682.0-based_on_SAMZA-670.patch
>
>
> This is a code refactoring task for the coordinator stream consumption: 
> 1. we have all the coordinator stream messages in a single class as static inner class, make them separate classes in a new package
> 2. Move all the common functionality of  (CheckpointManager, ChangelogMappingManager, HostAffinityManager) to a base class (bootstrap, message type) etc. We can enough data now to understand the pattern to do this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)