[
https://issues.apache.org/jira/browse/CASSANDRA-9802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626650#comment-14626650
]
Benjamin Lerer commented on CASSANDRA-9802:
-------------------------------------------
Sorry, let me try to be clearer.
To detect that the query involve paging, cqlsh will need to parse the query to
find the functions and checks if those functions are system aggregates or UDA.
It is doable but it will add a lot of logic to cqlsh.
SelectStatement already knows when a query is an aggregate one.
A simple solution would be to have a check in SelectStatement for aggregate
queries. If the page size is lower than a fix threshold (e.g. 5000), the page
size specified by the client is ignored and a page size of 5000 is used.
I think that it will be probably more reliable than to change cqlsh.
> Better page size for aggregates in cqlsh
> ----------------------------------------
>
> Key: CASSANDRA-9802
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9802
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Benjamin Lerer
> Priority: Minor
> Fix For: 3.x
>
>
> As discussed in CASSANDRA-9724, cqlsh uses a small page size (100) which
> makes sense for "normal" queries since you don't want to flood the terminal,
> but is quite sub-optimal for aggregates where the page size is used as the
> internal page size for the aggregate (there is thus no terminal flooding
> concerns and a page size of 100 is too low).
> We should thus make cqlsh use a bigger page size (stick with the python
> driver default for instance) when dealing with aggregate queries. According
> to Tyler:
> bq. it's not trivial, but it is possible. It should take a day or less of
> work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
