You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@samza.apache.org by "Yi Pan (Data Infrastructure) (JIRA)" <ji...@apache.org> on 2015/10/12 19:57:06 UTC

[jira] [Assigned] (SAMZA-793) Configure rewriter should be moved back to JobRunner

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

Yi Pan (Data Infrastructure) reassigned SAMZA-793:
--------------------------------------------------

    Assignee: Yi Pan (Data Infrastructure)

> Configure rewriter should be moved back to JobRunner
> ----------------------------------------------------
>
>                 Key: SAMZA-793
>                 URL: https://issues.apache.org/jira/browse/SAMZA-793
>             Project: Samza
>          Issue Type: Bug
>    Affects Versions: 0.10.0
>            Reporter: Yi Pan (Data Infrastructure)
>            Assignee: Yi Pan (Data Infrastructure)
>             Fix For: 0.10.0
>
>
> SAMZA-465 moved the config rewriter logic to JobCoordinator, which is not necessary, and potentially blocks any re-configuration needed before starting the coordinator stream systems. For static configuration rewriter, it would make sense to keep the rewriter logic in JobRunner.



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