[
https://issues.apache.org/jira/browse/CASSANDRA-3702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281727#comment-13281727
]
Sam Tunnicliffe commented on CASSANDRA-3702:
--------------------------------------------
I didn't think the overriding the key bounds would cause a problem, as queries
of the form
{{SELECT COUNT(*) FROM <cf> WHERE key='foo'}} and {{SELECT COUNT(*) FROM <cf>
WHERE key in ('foo', 'bar')}}
aren't treated as key range queries and so go down the branch that uses
getSlice(). However, I'd overlooked the token() function
(and, I imagine, behaviour when using OrderPreservingPartitioner) where a key
range can be specified.
Am I right that the issue with not paging within internal rows is that
fetching/materialising PAGE_COUNT_SIZE wide rows could still present a problem
by blowing up memory usage? If so, I could rework to add paging within the rows
(and fix the token()/range queries), or given your comment re: CASSANDRA-2478,
do you think it'd be better to just abandon this patch and close the ticket as
a "won't fix"?
> CQL count() needs paging support
> --------------------------------
>
> Key: CASSANDRA-3702
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3702
> Project: Cassandra
> Issue Type: Sub-task
> Components: Tools
> Reporter: Nick Bailey
> Assignee: Sam Tunnicliffe
> Labels: cql3, lhf
> Fix For: 1.1.2
>
> Attachments: v1-0001-CASSANDRA-3702-CQL-count-needs-paging-support.txt
>
>
> Doing
> {noformat}
> SELECT count(*) from <cf>;
> {noformat}
> will max out at 10,000 because that is the default limit for cql queries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
