--
Olivier Michallat
Driver & tools engineer, DataStax
To unsubscribe from this group and stop receiving emails from it, send an email to java-driver-us...@lists.datastax.com.
We are using Cassandra 1.2.18.1 with the Datastax Driver 2.1.4.
Thanks.my requirement is to get all available rows ,without putting too much load on the server. For C* 1.x,does the driver ensure that background queries fetch the next set of records when the iterator has finished with current set?
--
Olivier Michallat
Driver & tools engineer, DataStax
Thanks. In my usecase, there are 3 partition keys (k1, k2,k3) and 2 clustering keys (c1,c2) . c1 is a timestamp and c2 is a GUID - i.e there could be many events for the same c1. The query uses only one partition at a time.
select * where k1=A and k2=B and K3=C and c1>=t1 and c1<=t2 limit 500
Following this approach, if i use c1>(latest TS from 1st query), some events that may have the same timestamp would be lost, while if we use c1>=(latest TS from 1st query), there could be some duplicates. I guess we need to filter these duplicates manually (comparing with previous resultset). Please confirm.
Further, if i just need to get c2 from this query (i.e resultset payload size per row is small) , is it safe to provide a high-enough limit (say limit 100,000) assuming we know the # of records would be not more than 50,000 per day, so that i dont have to deal with manual pagination.