[
https://issues.apache.org/jira/browse/CASSANDRA-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133471#comment-18133471
]
Michael Semb Wever commented on CASSANDRA-11745:
------------------------------------------------
Yes, because 6.0-alpha2 and 6.0-alpha3 (indev_6_0_x) broke wire compatibility
and the latter isn't released yet.
This is expected to be fixed once 6.0-alpha3 is released and
https://github.com/apache/cassandra-dtest/blob/trunk/upgrade_tests/upgrade_manifest.py#L189
is updated. We have no good process AFAIK to deal with these changes and CI…
There can ofc be other issues in there that unintentionally i've missed, but I
don't think so.
> Add bytes limit to queries and paging
> -------------------------------------
>
> Key: CASSANDRA-11745
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11745
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Legacy/Core
> Reporter: Richard Low
> Assignee: Michael Semb Wever
> Priority: Normal
> Fix For: 6.0, 6.0-alpha3, 7.0
>
> Attachments:
> ci_summary_thelastpickle_mck-CASSANDRA-11745-6.0_62.html,
> ci_summary_thelastpickle_mck-CASSANDRA-11745-6.0_83.html,
> results_details_thelastpickle_mck-CASSANDRA-11745-6.0_62.tar.xz,
> results_details_thelastpickle_mck-CASSANDRA-11745-6.0_83.tar.xz
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> 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
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
