[
https://issues.apache.org/jira/browse/CASSANDRA-14956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-14956:
----------------------------------------
Status: Patch Available (was: Open)
Patch to change the page trimming for DISTINCT range queries to simply remove
the first row from the page.
||branch||CI||
|[14956-2.2|https://github.com/beobal/cassandra/tree/14956-2.2]|[circle|https://circleci.com/gh/beobal/workflows/cassandra/tree/cci%2F14956-2.2]|
> Paged Range Slice queries with DISTINCT can drop rows from results
> ------------------------------------------------------------------
>
> Key: CASSANDRA-14956
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14956
> Project: Cassandra
> Issue Type: Bug
> Components: CQL/Interpreter
> Reporter: Sam Tunnicliffe
> Assignee: Sam Tunnicliffe
> Priority: Major
> Fix For: 2.2.14
>
>
> If we have a partition where the first CQL row is fully deleted (possibly via
> TTLs), and that partition happens to fall on the page boundary of a paged
> range query which is using SELECT DISTINCT, the next live partition *after*
> it is omitted from the result set. This is due to over fetching of the pages
> and a bug in trimming those pages where overlap occurs.
> This does not affect 3.0+.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
