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

• Type: New Feature
• Status: Resolved
• Priority: Normal
• Resolution: Duplicate
• Fix Version/s: 3.0 beta 1
• Component/s: Legacy/CQL, Legacy/Local Write-Read Paths
• Assignee: Sam Tunnicliffe
• Reporter: Bryn Cooke

Authors

Sam Tunnicliffe

• Created: 25/Mar/15 17:11
• Updated: 16/Apr/19 09:31
• Resolved: 11/Aug/15 17:23

Description

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.

Issue Links

• Is contained by: CASSANDRA-9459 SecondaryIndex API redesign