You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/04/23 21:31:38 UTC
[jira] [Commented] (REEF-278) Support ProtocolBuffer ClassHierarchy
merge in Java Tang
[ https://issues.apache.org/jira/browse/REEF-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509638#comment-14509638 ]
Hudson commented on REEF-278:
-----------------------------
SUCCESS: Integrated in Reef-pull-request-windows #255 (See [https://builds.apache.org/job/Reef-pull-request-windows/255/])
[REEF-278] Support ClassHierarchy Merge between CLR and JVM (jwang98052: rev 54609ab4ed30f283759358b4ad2c00dcb7315657)
* lang/cs/Org.Apache.REEF.Tests/ConfigFiles/evaluator.conf
* lang/cs/Org.Apache.REEF.Tests/Org.Apache.REEF.Tests.csproj
* lang/java/reef-tang/tang/src/main/java/org/apache/reef/tang/implementation/protobuf/ProtocolBufferClassHierarchy.java
> Support ProtocolBuffer ClassHierarchy merge in Java Tang
> --------------------------------------------------------
>
> Key: REEF-278
> URL: https://issues.apache.org/jira/browse/REEF-278
> Project: REEF
> Issue Type: New Feature
> Components: Tang, Tang.NET
> Reporter: Julia
> Assignee: Julia
>
> The Configuration serialized from .Net and then deserialized back at java side contains ProtocolBufferClassHierarchy object. Currently Java Tang doesn't support ProtocolBufferClassHierarchy merge. That result in not able to merge Configurations deserialized from CLR.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)