cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10376) Fix upgrade_tests/
Date Fri, 02 Oct 2015 15:05:27 GMT


Sylvain Lebresne commented on CASSANDRA-10376:

For info, I tried my suggesting above, but the paging test now seems to run into CASSANDRA-10381
(on the 2.1 nodes), which seems to be a genuine 2.1 bug, so I'll check if we can easily fix
that issue first.

> Fix upgrade_tests/
> --------------------------------------------------------------------------
>                 Key: CASSANDRA-10376
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Aleksey Yeschenko
>            Assignee: Blake Eggleston
>             Fix For: 3.0.0 rc2
> Follow-up to CASSANDRA-10354 to fix the related upgrade issue.
> To quote [~bdeggleston]:
> {quote}
> So the failure is caused by an edge case where a names filter is used in a paging query
against a table that needs SinglePartitionNamesCommand instances converted to SinglePartitionSliceCommand
instances in order to be converted to legacy read commands.
> If the previous read returned all requested clusterings and a number of rows equal to
the page size, the subsequent read would have an empty clustering names filter. When an empty
clustering names filter is converted to a slice filter, the slice filter is created with Slices.ALL.
> {quote}

This message was sent by Atlassian JIRA

View raw message