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

Posted to dev@reef.apache.org by "Sergiy Matusevych (JIRA)" <ji...@apache.org> on 2017/07/20 01:21:00 UTC

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

Sergiy Matusevych created REEF-1835:
---------------------------------------

             Summary: 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


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)