[
https://issues.apache.org/jira/browse/STREAMS-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176942#comment-14176942
]
ASF GitHub Bot commented on STREAMS-195:
----------------------------------------
GitHub user robdouglas opened a pull request:
https://github.com/apache/incubator-streams/pull/106
STREAMS-195 | Added try/catch around ID addition process to ensure that ...
...a single malformed ID doesn't derail an entire Stream
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/robdouglas/incubator-streams STREAMS-195
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-streams/pull/106.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 #106
----
commit d4f6009979401d324949b9e7783c5e7ea381299e
Author: Robert Douglas <[email protected]>
Date: 2014-10-20T14:43:29Z
STREAMS-195 | Added try/catch around ID addition process to ensure that a
single malformed ID doesn't derail an entire Stream
----
> 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)
