[CASSANDRA-9196] Do not rebuild indexes if no columns are actually indexed

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 2.0.15, 2.1.5
• Assignee: Sergio Bossa
• Reporter: Sergio Bossa

Authors

Sergio Bossa

Reviewers

Sam Tunnicliffe

• Created: 15/Apr/15 18:16
• Updated: 16/Apr/19 09:31
• Resolved: 21/Apr/15 11:43

Description

When rebuilding secondary indexes, the index task is executed regardless if the actual SecondaryIndex#indexes(ByteBuffer ) implementation of any index returns true for any column, meaning that the expensive task of going through all sstables and related rows will be executed even if in the end no column/row will be actually indexed.

This is a huge performance hit when i.e. bootstrapping with large datasets on tables having custom secondary index implementations whose indexes() implementation might return false.

Issue Links

• relates to: CASSANDRA-9281 Index selection during rebuild fails with certain table layouts.
• relates to: CASSANDRA-9314 Overload SecondaryIndex#indexes to accept the column definition