[
https://issues.apache.org/jira/browse/STREAMS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16549297#comment-16549297
]
ASF GitHub Bot commented on STREAMS-605:
----------------------------------------
rawkintrevo commented on issue #455: resolves STREAMS-605
URL: https://github.com/apache/streams/pull/455#issuecomment-406284092
lgtm
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Implement Callable interface on a few twitter providers
> -------------------------------------------------------
>
> Key: STREAMS-605
> URL: https://issues.apache.org/jira/browse/STREAMS-605
> Project: Streams
> Issue Type: Improvement
> Reporter: Steve Blackmon
> Assignee: Steve Blackmon
> Priority: Major
>
> When interfacing with a Provider directly, we wind up needing a lot of
> boilerplate to get the resulting data.
> It would be useful to be able to directly access a full resultset produced
> with readAll as underlying document objects (not datums) just by submitting a
> provider to a java executorservice.
> Also this would allow for a provider to be run with a timeout chosen at
> run-time.
> Implement Callable interface on a few twitter providers as a proof of
> concept. Shouldn’t need to interfere with the other interfaces. If the
> community likes this approach we can roll it out more broadly and perhaps add
> Callable to the StreamsProvider interface.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
