[ https://issues.apache.org/jira/browse/CASSANDRA-14956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757569#comment-16757569 ]
Joseph Lynch commented on CASSANDRA-14956: ------------------------------------------ [~beobal] I think that the merge up to trunk broke trunk test runs (e.g. [7d138e20|https://circleci.com/gh/jolynch/cassandra/415]). I think it has to do with re-using the data directory from {{cassandra-murmur.yaml}}, debugging it now but do you think we need a separate ticket for fixing that test or I can just submit a fixup patch here? > 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.1.21, 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