Thanks once again Jonathan, I don't mind switching to an updated API call.
Was there any known issue like I described with the get_key_range method? Could the use of certain start/end keys, return counts or consistency levels contibute to the issue I'm seeing? Best Regards, Jon On Fri, Mar 12, 2010 at 1:53 PM, Jonathan Ellis <jbel...@gmail.com> wrote: > get_key_range is deprecated. You should use get_range_slice. > > On Fri, Mar 12, 2010 at 3:59 PM, Jon Graham <sjclou...@gmail.com> wrote: > > Hello, > > > > When using the get_key_range method with ConsistencyLevel.ONE an entire > > block of keys is not returned. > > I loop over the get_key_range method, advancing the start key after each > > call (requesting 8K keys per call). > > > > When running the program several times, I got the same results with large > > key blocks not returned. > > > > Then, I change the program to use ConsistencyLevel.ALL, then all the keys > > are returned as expected. > > > > Change the program back to use ConsistencyLevel.ONE and all the keys are > now > > returned. > > > > Has anyone else seen this issue? > > > > I would have expected ConsistencyLevel.ONE to be able to return all the > > keys. My 6 node cluster uses > > a replication factor of 3. > > > > Thanks for your help, > > Jon > > >
