You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@samza.apache.org by "Yi Pan (Data Infrastructure) (JIRA)" <ji...@apache.org> on 2017/04/06 17:08:42 UTC
[jira] [Resolved] (SAMZA-1094) Removal of MessageEnvelope class
from the top-level API
[ https://issues.apache.org/jira/browse/SAMZA-1094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yi Pan (Data Infrastructure) resolved SAMZA-1094.
-------------------------------------------------
Resolution: Fixed
Fix Version/s: 0.13.0
> Removal of MessageEnvelope class from the top-level API
> -------------------------------------------------------
>
> Key: SAMZA-1094
> URL: https://issues.apache.org/jira/browse/SAMZA-1094
> Project: Samza
> Issue Type: Bug
> Reporter: Yi Pan (Data Infrastructure)
> Assignee: Prateek Maheshwari
> Fix For: 0.13.0
>
>
> After SAMZA-1073 has removed the MessageEnvelope as the bounded type parameter to MessageStream, the only usage of MessageEnvelope class is mainly at ingress and egress streams of a graph.
> However, w/ further functions to do the following:
> a) extract a key from an unbound type M
> b) extract a message body from an unbound type M
> c) re-construct an unbound type M from an IncomingMessageEnvelope
> It would be possible to remove the interface class MessageEnvelope all together from the API.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)