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

Posted to commits@samza.apache.org by "Fred Ji (JIRA)" <ji...@apache.org> on 2017/04/19 23:27:04 UTC

[jira] [Commented] (SAMZA-1224) Revert job coordinator factory config to the old format

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

Fred Ji commented on SAMZA-1224:
--------------------------------

That's kind of pain for config compatibility. Once it is introduced, it is very hard to remove it. 

I think we may have to keep both if either one was exposed to the clients. 

> Revert job coordinator factory config to the old format
> -------------------------------------------------------
>
>                 Key: SAMZA-1224
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1224
>             Project: Samza
>          Issue Type: Bug
>            Reporter: Navina Ramesh
>            Assignee: Navina Ramesh
>             Fix For: 0.13.0
>
>
> We seemed to have introduced "job-coordinator.factory" and "job-coordinationService.factory" configs (in SAMZA-1080). The format is different from what we have today. I think this should be reverted back to "job.coordinator.factory" and "job.coordinationService.factory". If and when we refactor all configs to a newer format, this can updated too. 
> Also, this currently breaks existing jobs using job.coordinator.factory.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)