[
https://issues.apache.org/jira/browse/CASSANDRA-18062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17711821#comment-17711821
]
Mike Adamson commented on CASSANDRA-18062:
------------------------------------------
I have looked at
StorageAttachedIndexDDLTest#concurrentTruncateWithIndexBuilding and
CompactionTest#testConcurrentIndexDropWithCompaction (just because they were
mentioned in the first comment). I ran each test > 100 times locally with no
failure. I will run the rest of the above locally to see if I can identify any
obvious failures and then start investigating the rest.
I fully agree that all of these need fixing before we merge to trunk but I
would prefer if we could work on these in parallel to the work on the main
tickets in 16052.
[~adelapena] WDYT to this option? I am happy if you would prefer to have these
fixed prior to the merge.
> On-disk string index with index building and on-disk query path
> ---------------------------------------------------------------
>
> Key: CASSANDRA-18062
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18062
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/SAI
> Reporter: Mike Adamson
> Assignee: Mike Adamson
> Priority: Normal
> Labels: SAI
> Fix For: NA
>
>
> An on-disk index for string (literal) datatypes. This index is used for the
> following datatypes:
> * UTF8Type
> * AsciiType
> * CompositeType
> * Frozen types
> This includes the ability to write the index to disk at index creation, by
> specific index rebuild and during SSTable compaction.
> Also the ability to query the on-disk index and combine the results with
> those from the in-memory indexes created by CASSANDRA-18058.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
