> Could you create one ?
> https://issues.apache.org/jira/browse/CASSANDRA
There's one already. See
https://issues.apache.org/jira/browse/CASSANDRA-3702 that redirect to
https://issues.apache.org/jira/browse/CASSANDRA-4415.
--
Sylvain
> It's not about columns, it's about rows, see example statement.
My bad, misread the CQL.
My jira search fu is poor, but I could not find an open ticket for paging row
counts. Could you create one ?
https://issues.apache.org/jira/browse/CASSANDRA
Cheers
-
Aaron Morton
Freela
It's not about columns, it's about rows, see example statement.
In QueryProcessor#processStatement it reads rows into list, then does
list.size()
2012/10/1 aaron morton
> CQL will read everything into List to make latter a count.
>
>
> From 1.0 onwards count paginated reading the columns. What v
> CQL will read everything into List to make latter a count.
From 1.0 onwards count paginated reading the columns. What version are you on ?
https://issues.apache.org/jira/browse/CASSANDRA-2894
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.co
Actually an easy way to put cassandra down is
select count(*) from A limit 1000
CQL will read everything into List to make latter a count.
2012/9/26 aaron morton
> Can you provide some information on the queries and the size of the data
> they traversed ?
>
> The default maximum size for a s
Can you provide some information on the queries and the size of the data they
traversed ?
The default maximum size for a single thrift message is 16MB, was it larger
than that ?
https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L375
Cheers
-
Aaron Morton
Free
Is there anything I can do on the configuration side to prevent nodes from
going OOM due to queries that will read large amounts of data and exceed the
heap available?
For the past few days of we had some nodes consistently freezing/crashing with
OOM. We got a heap dump into MAT and figured ou
