[
https://issues.apache.org/jira/browse/CASSANDRA-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14005276#comment-14005276
]
Benedict commented on CASSANDRA-7279:
-------------------------------------
Do you mean ABTC? Pretty sure ABSC treats it correctly; probably when slicing
we should use the max of (previous slice end) and (new slice start) for the
bound of the new iterator. I'd kind of like to fix this in a similar way to how
we deal with it in ABSC though, although it would be more work (so probably
best left until later); in trunk we could use the new SearchIterator (with some
small tweaks) to solve the problem by always using the current position as a
lower bound for the search for the next lower bound.
> MultiSliceTest.test_with_overlap* unit tests failing in trunk
> -------------------------------------------------------------
>
> Key: CASSANDRA-7279
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7279
> Project: Cassandra
> Issue Type: Bug
> Components: Tests
> Reporter: Michael Shuler
> Assignee: Benedict
> Priority: Minor
> Fix For: 2.1 rc1
>
>
> Example:
> https://cassci.datastax.com/job/trunk_utest/623/testReport/org.apache.cassandra.thrift/MultiSliceTest/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
