You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2015/04/22 07:53:59 UTC

[jira] [Resolved] (REEF-128) Replace the protocol buffer use in the runtime API with POJOs

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

Markus Weimer resolved REEF-128.
--------------------------------
    Resolution: Fixed

Resolved via [#145|https://github.com/apache/incubator-reef/pull/145]

> Replace the protocol buffer use in the runtime API with POJOs
> -------------------------------------------------------------
>
>                 Key: REEF-128
>                 URL: https://issues.apache.org/jira/browse/REEF-128
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF-Common
>    Affects Versions: 0.10
>            Reporter: Markus Weimer
>            Assignee: Brian Cho
>            Priority: Minor
>
> We currently use Protocol Buffers between REEF and any particular runtime implementation ({{reef-runtime-local}},{{reef-runtime-yarn}}, {{reef-runtime-mesos}} and {{reef-runtime-hdinsight}}). We choose this approach based on the assumption that there might be a process boundary between the runtime implementation and the rest of the Driver. 
> However, that assumption hasn't been true for any of the runtimes we have so far. Hence, the use of Protocol Buffers for this API complicates matters for no gain. It would therefore be a good idea to drop it and replace the API with a standard, Plain Old Java Object (POJO) based approach.
> This refactoring would be an excellent, if somewhat painful, way to understand the guts of REEF for new committers and contributors.



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