You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@streams.apache.org by "Steve Blackmon (JIRA)" <ji...@apache.org> on 2016/12/17 20:08:58 UTC

[jira] [Resolved] (STREAMS-466) Twitter Providers should be smarter about setting count based on value of max_items and other context

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

Steve Blackmon resolved STREAMS-466.
------------------------------------
    Resolution: Fixed

> Twitter Providers should be smarter about setting count based on value of max_items and other context
> -----------------------------------------------------------------------------------------------------
>
>                 Key: STREAMS-466
>                 URL: https://issues.apache.org/jira/browse/STREAMS-466
>             Project: Streams
>          Issue Type: Bug
>            Reporter: Steve Blackmon
>            Assignee: Steve Blackmon
>             Fix For: 0.4.1
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Twitter Providers should be smarter about setting count based on value of max_items and other context.
> Currently count gets set to 200 by TwitterFollowingProvider even when idsOnly is true and max_items is 5000



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