[
https://issues.apache.org/jira/browse/CASSANDRA-9802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626703#comment-14626703
]
Sylvain Lebresne commented on CASSANDRA-9802:
---------------------------------------------
bq. If the user as set is page size to 50 what should we do?
Use 50 everywhere. 99.3% of users probably won't ever change cqlsh paging
defaults ever so it's ok if we're not perfect there. But here's the deal:
people will use aggregates from cqlsh, and the default will be
under-performing, so I'm just suggesting to change it if that's easy (I do not
know what this entails as I do not know cqlsh code). I don't want to boil the
ocean for no reason. If doing so adds too much complexity to cqlsh, we can
forget about it.
> 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)
