You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alex Petrov (JIRA)" <ji...@apache.org> on 2016/08/03 19:14:20 UTC
[jira] [Created] (CASSANDRA-12374) Can't rebuild SASI index
Alex Petrov created CASSANDRA-12374:
---------------------------------------
Summary: Can't rebuild SASI index
Key: CASSANDRA-12374
URL: https://issues.apache.org/jira/browse/CASSANDRA-12374
Project: Cassandra
Issue Type: Bug
Reporter: Alex Petrov
There's been no real requirement for that so far.
As [~beobal] has pointed out, it's not a big issue, since that only could be needed when index files are lost, data corruption on disk (hardware issue) has occurred or there was a bug that'd require an index rebuild.
During {{rebuild_index}} task, indexes are only "marked" as removed with {{SecondaryIndexManager::markIndexRemoved}} and then {{buildIndexesBlocking}} is called. However, since SASI keeps track of SSTables for the index, it's going to filter them out with {{.filter((sstable) -> !sasi.index.hasSSTable(sstable))}} in {{SASIIndexBuildingSupport}}.
If I understand the logic correctly, we have to "invalidate" (drop data) right before we re-index them. This is also a blocker for [CASSANDRA-11990] since without it we can't have an upgrade path.
I have a patch ready in branch, but since it's a bug, it's better to have it released earlier and for all branches affected.
cc [~xedin]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)