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 2015/12/04 21:18:11 UTC

[jira] [Updated] (CASSANDRA-9128) Flush system.IndexInfo after index state changed

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

Sam Tunnicliffe updated CASSANDRA-9128:
---------------------------------------
    Component/s: CQL

> Flush system.IndexInfo after index state changed
> ------------------------------------------------
>
>                 Key: CASSANDRA-9128
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9128
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Minor
>             Fix For: 2.0.15, 2.1.5
>
>         Attachments: 9128.txt
>
>
> We don't force a flush of {{system.IndexInfo}} after updating it by marking an index as built. This may lead to indexes being unnecessarily rebuilt following a disorderly shutdown.
> We also don't update it after an index is removed, but that's probably less of an issue as we do flush {{system.schema_columns}} after removing the index, so those won't get rebuilt.



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