[CASSANDRA-10604] Secondary index metadata is not reloaded when table is altered

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.0.0
• Component/s: Feature/2i Index, Legacy/CQL, Legacy/Distributed Metadata
• Severity: Normal
• Assignee: Sam Tunnicliffe
• Reporter: Tom Hobbs

Authors

Sam Tunnicliffe

Reviewers

Tom Hobbs

• Created: 27/Oct/15 18:38
• Updated: 16/Apr/19 09:30
• Resolved: 28/Oct/15 17:31

Description

The javadocs for Index.getMetadataReloadTask() state the following:

Returns a task to reload the internal metadata of an index.
Called when the base table metadata is modified or when the configuration of the Index is updated.

However, altering a table does not result in the reload task being executed. I think the root of the problem is that in SecondaryIndexManager.reloadIndex(), we only execute the reload task when the old IndexMetadata does not equal the current IndexMetadata. Altering the table does not change the index metadata, so this check always fails.

This especially affects per-row secondary indexes, where the index may need to handle columns being added or dropped.