streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Ebanks (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (STREAMS-195) TwitterTimelineProvider#consolidateToIDs should handle null values
Date Tue, 21 Oct 2014 14:47:34 GMT

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

Ryan Ebanks resolved STREAMS-195.
---------------------------------
    Resolution: Done

> TwitterTimelineProvider#consolidateToIDs should handle null values
> ------------------------------------------------------------------
>
>                 Key: STREAMS-195
>                 URL: https://issues.apache.org/jira/browse/STREAMS-195
>             Project: Streams
>          Issue Type: Bug
>            Reporter: Robert Douglas
>
> As a Stream executor, I should not have a single null or empty value derail an entire
Stream's update cycle. Instead, a try/catch needs to be put around the Long instantiation
so that troublesome IDs do not affect Stream operation.
> Acceptance Criteria:
> - A null, empty, or non-number can be passed into the Provider and it does not throw
an exception



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

Mime
View raw message