I have not benchmarked this. I suggest trying both and letting us know. :)
On Thu, Oct 14, 2010 at 2:03 PM, Narendra Sharma
wrote:
> Thanks Jonathan.
>
> Another related question is if I need to fetch only 1 row then what will be
> the difference between the performance of get_slice vs get_range
Thanks Jonathan.
Another related question is if I need to fetch only 1 row then what will be
the difference between the performance of get_slice vs get_range_slices.
The reason for this question is that we are using some code that uses
get_range_slices. We have option of forcing it to use count=1
get_range_slices never does "searching."
the performance of those two predicates is equivalent, assuming a row
"start key" actually exists.
On Thu, Oct 14, 2010 at 1:09 PM, Narendra Sharma
wrote:
> Hi,
>
> I am using Cassandra 0.6.5. Our application uses the get_range_slices to get
> rows in the
Hi,
I am using Cassandra 0.6.5. Our application uses the get_range_slices to get
rows in the given range.
Could someone please explain how get_range_slices works internally esp when
a count parameter (value = 1) is also specified in the SlicePredicate? Does
Cassandra first search all in the given
