The count you specify is the worst case, so if you can't even allocate a List to handle it, you shouldn't be specifying such a high count. Better find that out immediately, then when your data set grows in production.
On Mon, Aug 15, 2011 at 8:15 AM, Patrik Modesto <patrik.mode...@gmail.com> wrote: > On Mon, Aug 15, 2011 at 15:09, Jonathan Ellis <jbel...@gmail.com> wrote: >> On Mon, Aug 15, 2011 at 7:13 AM, Patrik Modesto >> <patrik.mode...@gmail.com> wrote: >>> PS: while reading the email before I'd send it, I've noticed the >>> keyRange.count =... is it possible that Cassandra is preallocating >>> some internal data acording the KeyRange.count parameter? >> >> That's exactly what it does. > > Ok. But is this pre-alocating really needed? Can't cassandra deduce > that it doesn't need that much space? > > Regards, > P. > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
