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 Thu, 22 May 2014 17:05:03 GMT

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

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

GitHub user robdouglas opened a pull request:

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

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

    ...o react appropriately to 'User' objects. The TwitterProfileProcessor can now process
on 'User' objects as well

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/26.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 #26
    
----
commit 8fed2088306e4439e6d64b0919939af6d927d0fc
Author: Robert Douglas <rdouglas@w2odigital.com>
Date:   2014-05-22T17:03:34Z

    STREAMS-88 | Updated the TwitterEventClassifier (and subsequent tests) to react appropriately
to 'User' objects. The TwitterProfileProcessor can now process on 'User' objects as well

----


> 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