You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Chris Riccomini (JIRA)" <ji...@apache.org> on 2014/10/24 23:21:38 UTC

[jira] [Commented] (SAMZA-444) Provide a Samza job data model for job coordinator

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

Chris Riccomini commented on SAMZA-444:
---------------------------------------

Also, ran with hello-samza, and all tests pass.

> Provide a Samza job data model for job coordinator
> --------------------------------------------------
>
>                 Key: SAMZA-444
>                 URL: https://issues.apache.org/jira/browse/SAMZA-444
>             Project: Samza
>          Issue Type: Sub-task
>          Components: container, yarn
>    Affects Versions: 0.9.0
>            Reporter: Chris Riccomini
>            Assignee: Chris Riccomini
>             Fix For: 0.9.0
>
>         Attachments: SAMZA-444-0.patch
>
>
> We currently have no data model for Samza jobs. As a result, we have really hacky code in JsonHelpers to handle (de)serializing job/container/task information between the job coordinator and its SamzaContainers.
> We should provide a proper data model for Samza jobs, which includes a Job, Container, and Task. The objects should contain relevant data that the job coordinator and SamzaContainer need. These classes should be written in Java, and use proper Jackson annotations to allow for easy (de)serialization.



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