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

Posted to commits@samza.apache.org by "Bharath Kumarasubramanian (Jira)" <ji...@apache.org> on 2020/05/27 03:31:00 UTC

[jira] [Updated] (SAMZA-2509) New config name to represent if split deployment feature is enabled

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

Bharath Kumarasubramanian updated SAMZA-2509:
---------------------------------------------
    Fix Version/s: 1.5

> New config name to represent if split deployment feature is enabled
> -------------------------------------------------------------------
>
>                 Key: SAMZA-2509
>                 URL: https://issues.apache.org/jira/browse/SAMZA-2509
>             Project: Samza
>          Issue Type: Sub-task
>            Reporter: Alan Zhang
>            Assignee: Alan Zhang
>            Priority: Major
>             Fix For: 1.5
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Currently, we are using `samza.cluster.based.job.coordinator.dependency.isolation.enabled` to show if Samza application enables split deployment on job coordinator.
> However, we also need one similar config for the job container with the same purpose. 
> So we'd better consolidate them to one generic config `job.split.deployment.enabled`.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)