You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Jake Maes (JIRA)" <ji...@apache.org> on 2017/06/08 15:25:18 UTC

[jira] [Resolved] (SAMZA-1329) Switch SamzaTaskProxy to use LocalityManager

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

Jake Maes resolved SAMZA-1329.
------------------------------
    Resolution: Fixed

Issue resolved by pull request 219
[https://github.com/apache/samza/pull/219]

> Switch SamzaTaskProxy to use LocalityManager
> --------------------------------------------
>
>                 Key: SAMZA-1329
>                 URL: https://issues.apache.org/jira/browse/SAMZA-1329
>             Project: Samza
>          Issue Type: Improvement
>            Reporter: Shanthoosh Venkataraman
>            Assignee: Shanthoosh Venkataraman
>             Fix For: 0.14.0
>
>
> TasksResource(/tasks/) in samza-rest is relying on JobModelManager.readJobModel to get jobmodel from (CoordinatorStream, jobConfig). This created binary dependencies of systemstreams defined in task.inputs of job config into samza-rest. Managing those dependencies is hard and unnecessary.
> This PR updates TasksResource to use LocalityManager to read task to container locality.
> In the future, this api will read jobmodel from SamzaMetadatasystem store.



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