[jira] [Commented] (CASSANDRA-12130) SASI related tests failing since CASSANDRA-11820

["Sam Tunnicliffe (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-12130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15361347#comment-15361347 ] 

Sam Tunnicliffe commented on CASSANDRA-12130:
---------------------------------------------

As this seems to be purely a problem with the unit tests, I haven't run the dtest CI jobs.

||branch||testall||
|[12130-3.9|https://github.com/beobal/cassandra/tree/12130-3.9]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12130-3.9-testall]|
|[12130-trunk|https://github.com/beobal/cassandra/tree/12130-trunk]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-12130-trunk-testall]|


> SASI related tests failing since CASSANDRA-11820
> ------------------------------------------------
>
>                 Key: CASSANDRA-12130
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12130
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>             Fix For: 3.x
>
>
> Since CASSANDRA-11820 was committed, a number of tests covering SASI have been failing. In both {{SASIIndexTest}} and {{SSTableFlushObserverTest}}, rows are built using an unsorted builder, which assumes that the columns are added in clustering order. However, in both cases, this is not true and the additional checks added to {{UnfilteredSerializer::serializeRowBody}} by CASSANDRA-11820 now trigger assertion errors and, ultimately, failing tests. 
> In addition, {{SASIIndexTest}} reuses a single table in multiple tests and performs its cleanup in the tear down method. When the assertion error is triggered, the tear down is not run, leaving data in the table and causing other failures in subsequent tests. 
> Patch to follow shortly...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)