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

Posted to commits@streams.apache.org by "Steve Blackmon (JIRA)" <ji...@apache.org> on 2016/10/25 04:22:58 UTC

[jira] [Closed] (STREAMS-160) Embed original source provider pojos inside datasift pojos if possible

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

Steve Blackmon closed STREAMS-160.
----------------------------------
       Resolution: Won't Fix
         Assignee: Steve Blackmon
    Fix Version/s: 0.4

> Embed original source provider pojos inside datasift pojos if possible
> ----------------------------------------------------------------------
>
>                 Key: STREAMS-160
>                 URL: https://issues.apache.org/jira/browse/STREAMS-160
>             Project: Streams
>          Issue Type: Improvement
>            Reporter: Steve Blackmon
>            Assignee: Steve Blackmon
>             Fix For: 0.4
>
>
> In any case where a multi-channel provider is supplying a json object or object fragment without modification from an upstream channel, there should be no need to model and serialize that fragment with classes in the multi-channel provider.  Rather, the appropriate class/interface from another provider should be embedded in the generated pojo.  Investigate whether this is possible for Instagram or any other channels datasift manages.



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