[
https://issues.apache.org/jira/browse/CASSANDRA-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279871#comment-15279871
]
Sylvain Lebresne commented on CASSANDRA-11745:
----------------------------------------------
For completeness sake, I'll mention that there has already be some discussion
about allowing to limit pages by bytes in CASSANDRA-6492. The main difference
that CASSANDRA-6492 is firstly concerned about making it easier for user to
pick a default page size even when you don't know the average size of you rows,
while this ticket is explicitly about case where row have very varying sizes.
Anyway, solving this issue would pretty much make CASSANDRA-6492 trivial, but
I'll remark that doing this properly imply changes to the intra-node protocol
so we might not be able to do it before 4.0.
I'll also remark that it is enough to only bother about paging since as a user
you can always stop reading at the first page if you so wish.
> Add bytes limit to queries and paging
> -------------------------------------
>
> Key: CASSANDRA-11745
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11745
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Richard Low
>
> For some data models, values may be of very different sizes. When querying
> data, limit by count doesn’t work well and leads to timeouts. It would be
> much better to limit by size of the response, probably by stopping at the
> first row that goes above the limit. This applies to paging too so you can
> safely page through such data without timeout worries.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
