On 6 August 2013 16:56, Keith Freeman <8fo...@gmail.com> wrote:
Your description makes me think that if new rows are added during the
> paging (i.e. between one select with token()'s and another), they might
> show up in the query results, right? (because the hash of the new row keys
> might fal
Ok, I get that, I'll have to find another way to sort out new rows.
Your description makes me think that if new rows are added during the
paging (i.e. between one select with token()'s and another), they might
show up in the query results, right? (because the hash of the new row
keys might fa
On 6 August 2013 15:12, Keith Freeman <8fo...@gmail.com> wrote:
> I've seen in several places the advice to use queries like to this page
> through lots of rows:
>
>
> select id from mytable where token(id) > token(last_id)
>
>
> But it's hard to find detailed information about how this works (at
I've seen in several places the advice to use queries like to this page
through lots of rows:
select id from mytable where token(id) > token(last_id)
But it's hard to find detailed information about how this works (at
least that I can understand -- the description in the Cassandra manual
is p
