John:
Will the third system be used if, e.g., the user has 1000 friends
and we request friends/ids WITHOUT pagination? Or must we include
pagination arguments even if 5000 to use the third system?
PJB
On Sep 7, 9:52 pm, John Kalucki jkalu...@gmail.com wrote:
I don't know all the details,
Eventually all requests will be handled by the third system, and the
second system will be removed from production. I don't know how this
will all play out. I'll see about getting Someone Who Knows to Do
Something.
-John
On Sep 7, 11:03 pm, PJB pjbmancun...@gmail.com wrote:
John:
Will the
Hi John,
On Sep 6, 3:59 pm, John Kalucki jkalu...@gmail.com wrote:
resources. There is minor pagination jitter in one case and a certain
class of row-count-based queries have to be deprecated (or limited)
and replaced with cursor-based queries to be practical. For now, we're
sending the
I don't know all the details, but my general understanding is that
these bulk followers calls have been heavily returning 503s for quite
some time now, and this is long established, but bad, behavior. These
bulk calls are hard to support and they need to be moved over to some
form of practical
I might add that, as ever, a message on status.twitter mentioning this
would really go a long way.
David.
On Sep 8, 5:27 am, David W. d...@botanicus.net wrote:
Hi John,
On Sep 6, 3:59 pm, John Kalucki jkalu...@gmail.com wrote:
resources. There is minor pagination jitter in one case and a
Thanks John. I appreciate the various ways of accessing this data, but when
you guys make updates to any of these, can you either do it in a beta
environment we can test in first, or earlier in the week? Where there are
very few Twitter engineers monitoring these lists during the weekends, and
For now, we're sending the row-count-queries queries back to the
second system, which is otherwise idle, but isn't consistent with the
first or third system.
Can you help us better understand what queries you're talking about?
Do you mean, e.g., that any queries that call for *ALL* friends/ids
On Sun, Sep 6, 2009 at 11:18 AM, Jesse Stay jesses...@gmail.com wrote:
Thanks John. I appreciate the various ways of accessing this data, but
when you guys make updates to any of these, can you either do it in a beta
environment we can test in first, or earlier in the week? Where there are
I don't understand how asking to release features earlier in the week is
asking a lot? What does that have to do with scaling social graphs?
Jesse
On Sun, Sep 6, 2009 at 2:49 PM, Nick Arnett nick.arn...@gmail.com wrote:
On Sun, Sep 6, 2009 at 11:18 AM, Jesse Stay jesses...@gmail.com wrote:
On Sun, Sep 6, 2009 at 1:52 PM, Jesse Stay jesses...@gmail.com wrote:
I don't understand how asking to release features earlier in the week is
asking a lot? What does that have to do with scaling social graphs?
I was referring to a beta environment.
Nick
John,
Thanks for the background info. Row count queries means to me the
summary friends and followers numbers displayed on the Twitter web
pages, and returned on the user profile via the API, correct? So, if I
am understanding you correctly, then the friends and followers that
we're getting back
11 matches
Mail list logo
