streams-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (STREAMS-371) Allow use of ids endpoints in TwitterFollowingProvider
Date Wed, 14 Oct 2015 21:11:05 GMT

    [ https://issues.apache.org/jira/browse/STREAMS-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957766#comment-14957766
] 

ASF GitHub Bot commented on STREAMS-371:
----------------------------------------

GitHub user steveblackmon opened a pull request:

    https://github.com/apache/incubator-streams/pull/263

    resolves STREAMS-371

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/steveblackmon/incubator-streams STREAMS-371

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-streams/pull/263.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 #263
    
----
commit 20e7b66171634b948daaa6d9cc119990fbeec50f
Author: Steve Blackmon <sblackmon@apache.org>
Date:   2015-10-14T20:36:44Z

    resolves STREAMS-371

----


> Allow use of ids endpoints in TwitterFollowingProvider
> ------------------------------------------------------
>
>                 Key: STREAMS-371
>                 URL: https://issues.apache.org/jira/browse/STREAMS-371
>             Project: Streams
>          Issue Type: Improvement
>            Reporter: Steve Blackmon
>            Assignee: Steve Blackmon
>
> Allow use of ids endpoints in TwitterFollowingProvider
> These ids have higher throughput than the endpoints the provider currently uses, at the
cost of getting only IDs rather than full profiles.



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

Mime
View raw message