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 2016/09/21 01:19:21 UTC

[jira] [Commented] (REEF-1570) Replace Avro dependency with protobuf in O.A.R.Utilities

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

Markus Weimer commented on REEF-1570:
-------------------------------------

Given the nature of the work and the code in question, can't we just inline the method bodies from {{AvroUtilities}} at their call site? And then remove them subsequently when we remove the Avro dependencies in those projects?

> Replace Avro dependency with protobuf in O.A.R.Utilities
> --------------------------------------------------------
>
>                 Key: REEF-1570
>                 URL: https://issues.apache.org/jira/browse/REEF-1570
>             Project: REEF
>          Issue Type: Sub-task
>          Components: REEF.NET
>    Affects Versions: 0.16
>            Reporter: Shravan Matthur Narayanamurthy
>            Assignee: Shravan Matthur Narayanamurthy
>              Labels: .net-core
>             Fix For: 0.16
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> O.A.R.Utilities is at the root of our dependency tree. As this has a dependency on Avro, it prevents any project from being .Net Core compliant without resolving the Avro issue. Resolving this will stage our Avro to protobuf conversion well. Also the number of dependencies there is to AvroUtilities is not much which also limits the scope of this work. So we should do this as one of the stages in our Avro to protobuf conversion perhaps after we resolve REEF-1569.



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