[jira] [Resolved] (STREAMS-260) FacebookPageFeedDataCollector should handle backoff strategy correctly

["Steve Blackmon (JIRA)" <ji...@apache.org>]

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

Steve Blackmon resolved STREAMS-260.
------------------------------------
       Resolution: Fixed
         Assignee: Robert Douglas
    Fix Version/s: 0.3

> FacebookPageFeedDataCollector should handle backoff strategy correctly
> ----------------------------------------------------------------------
>
>                 Key: STREAMS-260
>                 URL: https://issues.apache.org/jira/browse/STREAMS-260
>             Project: Streams
>          Issue Type: Bug
>            Reporter: Robert Douglas
>            Assignee: Robert Douglas
>             Fix For: 0.3
>
>
> As a Stream user, I should be able to correctly respond to Facebook rate limit exceptions. Currently, any error from the Facebook Graph API results in a call to the exponential backoff strategy. This is fine if we are actually getting requests throttled/rate limited, but can result in very slow Stream completion if the error is related to something else (like a bad Page ID).
> We need to ensure that we only use the backoff strategy when we are being rate limited.
> *Acceptance Criteria:*
> - Determine which error codes represent potential rate limiting/throttling exceptions
> - Only call the backoff when our requests are being throttled.



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