incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patricio Echag├╝e <patric...@gmail.com>
Subject Re: Efficiency of hector's setRowCount
Date Thu, 13 Oct 2011 16:15:21 GMT
Hi Don. No it will not. IndexedSlicesQuery will read just the amount of rows
specified by RowCount and will go to the DB to get the new page when needed.

SetRowCount is doing indexClause.setCount(rowCount);

On Mon, Oct 10, 2011 at 3:52 PM, Don Smith <dsmith@likewise.com> wrote:

> Hector's IndexedSlicesQuery has a setRowCount method that you can use to
> page through the results, as described in https://github.com/rantav/**
> hector/wiki/User-Guide <https://github.com/rantav/hector/wiki/User-Guide>.
>
>     rangeSlicesQuery.setRowCount(**1001);
>      .....
>     rangeSlicesQuery.setKeys(**lastRow.getKey(),  "");
>
> Is it efficient?  Specifically, suppose my query returns 100,000 results
> and I page through batches of 1000 at a time (making 100 executes of the
> query). Will it internally retrieve all the results each time (but pass only
> the desired set of 1000 or so to me)? Or will it optimize queries to avoid
> the duplication?      I presume the latter. :)
>
> Can IndexedSlicesQuery's setStartKey method be used for the same effect?
>
>   Thanks,  Don
>

Mime
View raw message