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/06/01 01:36:12 UTC

[jira] [Commented] (STREAMS-95) TwitterProfileProcessor needs to send a user ID in each StreamsDatum

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

Steve Blackmon commented on STREAMS-95:
---------------------------------------

looks like this merged in commit c55e33d54d66a1d0c0675542a9d9de02c438ffa9

marking it resolved

> TwitterProfileProcessor needs to send a user ID in each StreamsDatum
> --------------------------------------------------------------------
>
>                 Key: STREAMS-95
>                 URL: https://issues.apache.org/jira/browse/STREAMS-95
>             Project: Streams
>          Issue Type: Task
>            Reporter: Robert Douglas
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> When the TwitterProfileProcessor encounters a Retweet or User object, it creates a new StreamsDatum that consists only of that user. The created StreamsDatum needs to also have that user's unique identifier (passed in via the constructor) so that we don't end up with duplicates down the stream



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