You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sam Tunnicliffe (JIRA)" <ji...@apache.org> on 2016/03/29 17:25:25 UTC

[jira] [Updated] (CASSANDRA-11453) CustomIndexTest fails intermittently

     [ https://issues.apache.org/jira/browse/CASSANDRA-11453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sam Tunnicliffe updated CASSANDRA-11453:
----------------------------------------
    Status: Patch Available  (was: Open)

Trivial patch makes all index names used in {{CustomIndexTest}} unique and adds logging of the underlying cause of a schema change exception.

||branch||testall||dtest||
|[11453-3.0|https://github.com/beobal/cassandra/tree/11453-3.0]|[testall|http://cassci.datastax.com/view/Dev/view/beobal/job/beobal-11453-3.0-testall]|N/A|


> CustomIndexTest fails intermittently
> ------------------------------------
>
>                 Key: CASSANDRA-11453
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11453
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Testing
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>             Fix For: 3.0.x, 3.x
>
>
> For example: http://cassci.datastax.com/job/cassandra-3.0_testall/460/testReport/org.apache.cassandra.index/CustomIndexTest/customExpressionForcesIndexSelection/
> This is due to a clash in index names as the cleanup of tables (and so also indexes) in the teardown of {{CQLTester}} is asynchronous.



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