[
https://issues.apache.org/jira/browse/CASSANDRA-11745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18133471#comment-18133471
]
Michael Semb Wever edited comment on CASSANDRA-11745 at 10/28/26, 8:23 AM:
---------------------------------------------------------------------------
Yes, because 6.0-alpha2 and 6.0-alpha3 (indev_6_0_x) broke compatibility and
the latter isn't released yet.
(You can see how in build 2646 once the commit was picked up on both edges of
6.0 and 7.0 indevs the test failures dropped from 1772 to 342.)
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.
There can ofc be other issues in there that unintentionally i've missed, but I
don't think so.
We have no good process AFAIK to deal with these changes and CI…
Should we be commenting out the upgrade paths until the release is made ? (and
creating a `6.0-alpha` beta-blocking ticket to uncomment them again?) 🤷🏼
was (Author: michaelsembwever):
Yes, because 6.0-alpha2 and 6.0-alpha3 (indev_6_0_x) broke 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.
There can ofc be other issues in there that unintentionally i've missed, but I
don't think so.
We have no good process AFAIK to deal with these changes and CI…
Should we be commenting out the upgrade paths until the release is made ? (and
creating a `6.0-alpha` beta-blocking ticket to uncomment them again?) 🤷🏼
> 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]
