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/06/30 13:38:00 UTC

[jira] [Updated] (CASSANDRA-18598) Use trie for literal index building

     [ https://issues.apache.org/jira/browse/CASSANDRA-18598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Adamson updated CASSANDRA-18598:
-------------------------------------
    Summary: Use trie for literal index building  (was: Use trie in BlockBalancedTreeRamBuffer)

> Use trie for literal index building
> -----------------------------------
>
>                 Key: CASSANDRA-18598
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-18598
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Mike Adamson
>            Priority: Normal
>
> The BlockBalancedTreeRamBuffer currently doesn't sort terms as they are added so the terms need sorting before they are added to the BlockBalancedTree.
> If we used a trie in place of the ByteBlockPool the terms would be sorted. They could also take advantage of the prefix compression in the trie which would allow larger segments on disk.
> If the requirement to sort was removed from the BlockBalancedTree we could remove the PointValues implementations that are needed by the Lucene sorter. This could allow for significant simplification of the codebase during the write phase.



--
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