You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Anupam (JIRA)" <ji...@apache.org> on 2016/01/28 02:19:39 UTC
[jira] [Updated] (REEF-1164) Refactor bridge as IPC between Java
and .NET
[ https://issues.apache.org/jira/browse/REEF-1164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anupam updated REEF-1164:
-------------------------
Description:
REEF driver logic is mainly implemented in Java. It is undesirable to implement driver core logic again and again as it is bug-prone and tricky. Further, YARN and MESOS provide Java based APIs.
For implementing driver in languages other than Java we propose an IPC based driver could be implemented in Java for which multiple remote drivers could be authored in users’ language of choice.
* This would clean up the API, make it less error prone.
* Make it easy to add driver API for a new language.
* Remove the tricky to debug .NET/Java surface area.
* Help us get Linux support for REEF .NET.
Potential break down for the work items:
* API specification for driver protocol in language agnostic manner. Avro is the choice of technology currently in REEF
* Communicate between .NET driver and Java remote driver using above API
* Split .NET driver out of process
was:
REEF driver logic is mainly implemented in Java and it is undesirable to implement the core logic which is bug-prone and tricky, again and again. Further YARN and MESOS provide Java based APIs.
For implementing driver in languages other than Java we propose an IPC based driver could be implemented in Java for which multiple remote drivers could be authored in users’ language of choice.
* This would clean up the API, make it less error prone.
* Make it easy to add driver API for a new language.
* Remove the tricky to debug .NET/Java surface area.
* This would help us get Linux support for REEF .NET.
> Refactor bridge as IPC between Java and .NET
> ---------------------------------------------
>
> Key: REEF-1164
> URL: https://issues.apache.org/jira/browse/REEF-1164
> Project: REEF
> Issue Type: New Feature
> Components: REEF Bridge, REEF Driver, REEF.NET Driver
> Reporter: Anupam
>
> REEF driver logic is mainly implemented in Java. It is undesirable to implement driver core logic again and again as it is bug-prone and tricky. Further, YARN and MESOS provide Java based APIs.
> For implementing driver in languages other than Java we propose an IPC based driver could be implemented in Java for which multiple remote drivers could be authored in users’ language of choice.
> * This would clean up the API, make it less error prone.
> * Make it easy to add driver API for a new language.
> * Remove the tricky to debug .NET/Java surface area.
> * Help us get Linux support for REEF .NET.
> Potential break down for the work items:
> * API specification for driver protocol in language agnostic manner. Avro is the choice of technology currently in REEF
> * Communicate between .NET driver and Java remote driver using above API
> * Split .NET driver out of process
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)