On Fri, Jul 3, 2009 at 8:53 PM, Evan Weaver wrote:
> (From talking on IRC):
>
> I think this boils down to the offset/limit vs. token/limit debate.
>
> Token/limit is fine in all cases for me, but you still have to be able
> to query the head of the list (with a limit, but no token) to get
> starte
On Fri, Jul 3, 2009 at 7:14 PM, Evan Weaver wrote:
> You can (once the API is fixed) make a client request the data from
> every replica on read. Which ever replica has the most recent value
> will be the value that's returned. That makes sure that reads and
> writes are consistently serialized
You can (once the API is fixed) make a client request the data from
every replica on read. Which ever replica has the most recent value
will be the value that's returned. That makes sure that reads and
writes are consistently serialized from the server's perspective, at
some performance cost.
Wea
FYI, Yahoo does an interesting thing in this case. They usually use
token pagination, but if a page displays limit 20 records, they
actually request limit 100 behind the scenes. The extra records are
used to generate deep links. So instead of just being able to go to
the next page:
prev | cur | ne
(From talking on IRC):
I think this boils down to the offset/limit vs. token/limit debate.
Token/limit is fine in all cases for me, but you still have to be able
to query the head of the list (with a limit, but no token) to get
started. Right now there is no facility for that on time-sorted colum
I'm evaluating a number of options to an rdbms for some of our facebook
games. A small, yet important number of queries require transactions. For
example we have auctions, and buying/purchasing of items with limited
quantities.
Are there knobs you can tweak to enforce consistency on a per query b
That requires you to know the timestamp, so you can't just ask for the
most recent one.
Evan
On Fri, Jul 3, 2009 at 6:02 PM, Jonathan Ellis wrote:
> get_columns_since
>
> On Fri, Jul 3, 2009 at 7:21 PM, Evan Weaver wrote:
>> This helps a lot.
>>
>> However, I can't find any API method that actual
get_columns_since
On Fri, Jul 3, 2009 at 7:21 PM, Evan Weaver wrote:
> This helps a lot.
>
> However, I can't find any API method that actually lets me do a
> slice query on a time-sorted column, as necessary for the second blog
> example. I get the following error on r789419:
>
> InvalidRequestEx
This helps a lot.
However, I can't find any API method that actually lets me do a
slice query on a time-sorted column, as necessary for the second blog
example. I get the following error on r789419:
InvalidRequestException: get_slice_from requires CF indexed by name
Evan
On Tue, May 19, 2009 at
