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

Posted to dev@reef.apache.org by "Julia (JIRA)" <ji...@apache.org> on 2015/08/08 04:08:46 UTC

[jira] [Assigned] (REEF-574) Eliminate Task Configuration deserialization/serialization at Java side

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

Julia reassigned REEF-574:
--------------------------

    Assignee: Julia

> Eliminate Task Configuration deserialization/serialization at Java side
> -----------------------------------------------------------------------
>
>                 Key: REEF-574
>                 URL: https://issues.apache.org/jira/browse/REEF-574
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF, REEF Bridge, REEF-Common
>            Reporter: Julia
>            Assignee: Julia
>
> Currently Task configuration is passed over the bridge as a string. At Java side, it is deserialized into a Configuration object with C# class hierarchy. Before it is passed over to Evaluator, it is serialized again into a string. 
> There are two issues:
> 1. When Task class contains a generic type, Java is not able to understand the class hierarchy from C#. That causes deserialization fail. 
> 2. Performance hit. It is not necessary to deseralize the Task Configuration and then serialize it again. 
> A proposed solution is to pass it directly to the .Net evaluator and let .Net Evaluator to desterilize it. Then there won't have any cross language issue. 



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