[jira] [Updated] (CASSANDRA-9041) Allow a PerRowSecondaryIndex to perform its index operation before the underlying data has been mutated

["Bryn Cooke (JIRA)" <ji...@apache.org>]

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

Bryn Cooke updated CASSANDRA-9041:
----------------------------------
    Summary: Allow a PerRowSecondaryIndex to perform its index operation before the underlying data has been mutated  (was: Allow a PerRowSecondaryIndex to perform it's index operation before the underlying data has been mutated)

> Allow a PerRowSecondaryIndex to perform its index operation before the underlying data has been mutated
> -------------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-9041
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9041
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Bryn Cooke
>
> The current PerRowSecondaryIndex receives its index event after the call to BTree.update. This means that it is impossible to write an index that eagerly removes stale index entries.
> It would be great to have some sort of preIndex method that gets called with the key and column family.
> In addition a postIndex method that is guaranteed to get called regardless if the actual BTree operation succeeds or not would allow cleanup in the event of error. 



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