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
wrote:
> On Mon, Aug 15, 2011 a
On Mon, Aug 15, 2011 at 15:09, Jonathan Ellis wrote:
> On Mon, Aug 15, 2011 at 7:13 AM, Patrik Modesto
> 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.cou
On Mon, Aug 15, 2011 at 7:13 AM, Patrik Modesto
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.
--
Jonathan Ell
"internal error" means an error on the server. check the server log for the
stacktrace.
On Wed, Apr 20, 2011 at 11:54 AM, Renato Bacelar da Silveira <
renat...@indabamobile.co.za> wrote:
> Hi all
>
> I am just augmenting the information on the following error:
>
> -- error --
