[
https://issues.apache.org/jira/browse/CASSANDRA-10376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965119#comment-14965119
]
Sylvain Lebresne commented on CASSANDRA-10376:
----------------------------------------------
So pushed the change above
[here|https://github.com/pcmanus/cassandra/commits/10376], and now that the
patch for CASSANDRA-10381 has been committed, I can confirm that this fixes the
test in question, so calling that branch officially ready for review.
> Fix upgrade_tests/paging_test.py:TestPagingData.static_columns_paging_test
> --------------------------------------------------------------------------
>
> Key: CASSANDRA-10376
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10376
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Aleksey Yeschenko
> Assignee: Blake Eggleston
> Fix For: 3.0.0
>
>
> 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
(v6.3.4#6332)
