You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Mike Adamson (Jira)" <ji...@apache.org> on 2023/12/13 15:46:00 UTC
[jira] [Commented] (CASSANDRA-18598) Use trie for literal index building
[ https://issues.apache.org/jira/browse/CASSANDRA-18598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17796358#comment-17796358 ]
Mike Adamson commented on CASSANDRA-18598:
------------------------------------------
Patches for this are here:
|[5.0|https://github.com/apache/cassandra/pull/2989]|[CI|https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/426/workflows/710a84d3-f22a-49bf-a2fa-a08e9c0ca7df]|
|[trunk|https://github.com/apache/cassandra/pull/2991]|[CI|https://app.circleci.com/pipelines/github/mike-tr-adamson/cassandra/427/workflows/1e6323c8-4533-4bf1-aa77-54b028893b68]|
> 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: 0.5h
> 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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org