[
https://issues.apache.org/jira/browse/STREAMS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177128#comment-14177128
]
ASF GitHub Bot commented on STREAMS-195:
----------------------------------------
Github user rbnks commented on the pull request:
https://github.com/apache/incubator-streams/pull/106#issuecomment-59803968
:+1:
> 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)
