streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (STREAMS-88) TwitterEventClassifier does not react as expected to 'User' objects
Date Tue, 20 May 2014 15:30:39 GMT

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

ASF GitHub Bot commented on STREAMS-88:
---------------------------------------

GitHub user robdouglas opened a pull request:

    https://github.com/apache/incubator-streams/pull/22

    STREAMS-88 | Modified the TwitterEventClassifier (and subsequent tests) ...

    ...to recognize 'User' objects. Added block in TwitterProfileProcessor to check to see
if the object we are operating on is a 'User' and if so, respond accordingly

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robdouglas/incubator-streams STREAMS-88

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-streams/pull/22.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #22
    
----
commit 366f3c72ceba4ee7b419a9abffc2efcfa95d1ea7
Author: Robert Douglas <rdouglas@w2odigital.com>
Date:   2014-05-20T15:28:26Z

    STREAMS-88 | Modified the TwitterEventClassifier (and subsequent tests) to recognize 'User'
objects. Added block in TwitterProfileProcessor to check to see if the object we are operating
on is a 'User' and if so, respond accordingly

----


> TwitterEventClassifier does not react as expected to 'User' objects
> -------------------------------------------------------------------
>
>                 Key: STREAMS-88
>                 URL: https://issues.apache.org/jira/browse/STREAMS-88
>             Project: Streams
>          Issue Type: Bug
>            Reporter: Robert Douglas
>
> In the event that we get a Twitter 'User' object, the TwitterEventClassifier treats it
as a tweet. This causes issues in serializers where we try to process that object using the
Tweet serializers.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message