[
https://issues.apache.org/jira/browse/CASSANDRA-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14007236#comment-14007236
]
Sylvain Lebresne commented on CASSANDRA-7279:
---------------------------------------------
We've always assumed it was the job of whomever built the slices (so mainly the
thrift code and the CQL3 code) to de-overlap (and make sure things were in the
right order). Wouldn't it be cleaner to keep it that way, i.e. to push the
deoverlapping in places of code that might generate overlapping slices (which
part of the code is doing that btw?), rather that pass the comparator every
time but having it null half of the time?
> 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: T Jake Luciani
> Priority: Minor
> Fix For: 2.1 rc1
>
> Attachments: 7279-trunk.txt, 7279-trunkv2.txt, 7279-trunkv3.txt,
> 7279-trunkv4.txt
>
>
> 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)
