[jira] [Resolved] (REEF-1835) Use stricter type constraints in Avro ProtocolSerializer

["Doug Service (JIRA)" <ji...@apache.org>]

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

Doug Service resolved REEF-1835.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 0.16

Resolved by pull request: https://github.com/apache/reef/pull/1337

> Use stricter type constraints in Avro ProtocolSerializer
> --------------------------------------------------------
>
>                 Key: REEF-1835
>                 URL: https://issues.apache.org/jira/browse/REEF-1835
>             Project: REEF
>          Issue Type: Improvement
>          Components: Wake.NET
>            Reporter: Sergiy Matusevych
>            Assignee: Sergiy Matusevych
>            Priority: Minor
>              Labels: refactor, refactoring
>             Fix For: 0.16
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> Current version of {{ProtocolSerializer.Read()}} method accepts _any_ type for the {{observer}} parameter, while internally it is always assumed to be of type {{IObserver<MessageInstance<?>>}}. We need tighter type constraints here - at least in the user-facing API.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)