[
https://issues.apache.org/jira/browse/CASSANDRA-12374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15427265#comment-15427265
]
Pavel Yaskevich commented on CASSANDRA-12374:
---------------------------------------------
bq. currently unqueriable indexes / are skipped.
Yes, that was intentional, because there is (and probably still isn't) a good
way to propagate exceptions in a meaningful way, so we've opted out to writing
to the log and returning 0 results instead.
> 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
> Assignee: 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)
