[
https://issues.apache.org/jira/browse/CASSANDRA-18598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Adamson updated CASSANDRA-18598:
-------------------------------------
Status: Ready to Commit (was: Review In Progress)
Final CI runs:
|[5.0|https://github.com/apache/cassandra/pull/2989]|[j11|https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/443/workflows/f5ab3823-ac34-41df-aefb-7779a7359735]|[j17|https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/443/workflows/f64736ff-8f79-4b98-bee4-6831188cb720]|
|[trunk|https://github.com/apache/cassandra/pull/2991]|[j11|https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/444/workflows/6c53718c-1898-449b-b2f3-4c1f365fd057]|[j17|https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/444/workflows/a19ee49b-76bd-452c-8ccd-4bdc68341264]|
> Use trie for literal index building
> -----------------------------------
>
> Key: CASSANDRA-18598
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18598
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/SAI
> Reporter: Mike Adamson
> Assignee: Mike Adamson
> Priority: Normal
> Fix For: 5.x
>
> Time Spent: 7h 50m
> Remaining Estimate: 0h
>
> The BlockBalancedTreeRamBuffer for numerics indexes uses a trie for building
> indexes in memory before flushing to disk. The RAMStringIndexer for literal
> indexes does not do this. It uses lucene classes to build the in memory index
> before flushing.
> We should combine both of the in-memory index builders and have them both use
> the trie.
--
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
