[jira] [Updated] (SAMZA-1203) Use ProcessorId instead of Zk node Id in JobModel generation

["Prateek Maheshwari (JIRA)" <ji...@apache.org>]

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

Prateek Maheshwari updated SAMZA-1203:
--------------------------------------
    Fix Version/s: 0.13.0

> Use ProcessorId instead of Zk node Id in JobModel generation
> ------------------------------------------------------------
>
>                 Key: SAMZA-1203
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1203
>             Project: Samza
>          Issue Type: Bug
>    Affects Versions: 0.13.0
>            Reporter: Xinyu Liu
>            Assignee: Navina Ramesh
>            Priority: Blocker
>             Fix For: 0.13.0
>
>
> when ZkJobCoordinator generates the jobModel, it's using Zk node Ids instead of the processorIds, as the code below: ZkJobCoordinator: 215-220:
>     List<String> containerIds = new ArrayList<>();
>     for (String processor : currentProcessors) {
>       String zkProcessorId = ZkKeyBuilder.parseIdFromPath(processor);
>       containerIds.add(zkProcessorId);
>     }
>     log.info("generate new job model: processorsIds: " + Arrays.toString(containerIds.toArray()));
> Later the StreamProcessor gets the containerModel, it's null. We need to use the processorId in the JobModel so StreamProcessors will work correctly.



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