[
https://issues.apache.org/jira/browse/CASSANDRA-6492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628304#comment-14628304
]
Tyler Hobbs edited comment on CASSANDRA-6492 at 7/15/15 4:21 PM:
-----------------------------------------------------------------
The difference is mostly in the amount of work and driver-level support.
With aggregates, we can pretty safely ignore user-specified page sizes because
it only affects Cassandra internally and doesn't change how the results are
returned.
For non-aggregate queries, we probably need to make some protocol changes, such
as using a page size of -1 to indicate that the server should select the page
size. I haven't thought through exactly how drivers would need to handle this
in a backwards-compatible-friendly way, but it seems like the issue is more
complex than for aggregates alone. Splitting out the work for aggregates could
let us commit that simpler part much sooner, and suboptimal aggregate page
sizes are what motivated us to get this done in the first place.
If we plan to not do either until 3.x, then I'm fine with doing them at the
same time, but I thought we might want to fix aggregates sooner than that.
was (Author: thobbs):
The difference is mostly in the amount of work and driver-level support.
With aggregates, we can pretty safely ignore user-specified page sizes because
it only affects Cassandra internally and doesn't change how the results are
returned.
For non-aggregate queries, we probably need to make some protocol changes, such
as using a page size of -1 to indicate that the server should select the page
size. I haven't thought through exactly how drivers would need to handle this
in a backwards-compatible-friendly way, but it seems like the issue is more
complex than for aggregates alone. Splitting out the work for aggregates could
let us commit that simpler part much sooner, and suboptimal aggregate page
sizes are what motivated us to get this done in the first place.
> Have server pick query page size by default
> -------------------------------------------
>
> Key: CASSANDRA-6492
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6492
> Project: Cassandra
> Issue Type: New Feature
> Components: API
> Reporter: Jonathan Ellis
> Assignee: Benjamin Lerer
> Priority: Minor
>
> We're almost always going to do a better job picking a page size based on
> sstable stats, than users will guesstimating.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
