You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Stefania (JIRA)" <ji...@apache.org> on 2016/08/02 03:06:20 UTC

[jira] [Commented] (CASSANDRA-12353) CustomIndexTest can still fail due to async cleanup

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

Stefania commented on CASSANDRA-12353:
--------------------------------------

There is possibly one "custom_index" still left at this [line|https://github.com/beobal/cassandra/commit/9ec9a061f6849b57f33e91b9d236ec3b2f92b016#diff-13cb97758bcb11cce8fc6f4cb1990dd6R374].

Otherwise +1.

> CustomIndexTest can still fail due to async cleanup
> ---------------------------------------------------
>
>                 Key: CASSANDRA-12353
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12353
>             Project: Cassandra
>          Issue Type: Test
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>
> CASSANDRA-11453 didn't quite go far enough in ensuring that indexes in {{CustomIndexTest}} are uniquely named. A couple of duplicates were missed which has lead to at least one failure (on trunk):
>  http://cassci.datastax.com/job/trunk_utest/1613/testReport/org.apache.cassandra.index/CustomIndexTest/customIndexRejectsExpressionSyntax/



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