Tyler Hobbs created CASSANDRA-10604:
---------------------------------------
Summary: Secondary index metadata is not reloaded when table is
altered
Key: CASSANDRA-10604
URL: https://issues.apache.org/jira/browse/CASSANDRA-10604
Project: Cassandra
Issue Type: Bug
Components: Core
Reporter: Tyler Hobbs
Assignee: Sam Tunnicliffe
Fix For: 3.x
The javadocs for {{Index.getMetadataReloadTask()}} state the following:
{quote}
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.
{quote}
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
