You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jason Rutherglen (JIRA)" <ji...@apache.org> on 2013/04/29 17:32:16 UTC
[jira] [Commented] (CASSANDRA-4324) Implement Lucene FST in for key
index
[ https://issues.apache.org/jira/browse/CASSANDRA-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644580#comment-13644580 ]
Jason Rutherglen commented on CASSANDRA-4324:
---------------------------------------------
What is the difference between the token and the key?
The FST could theoretically cache (due to compression efficiency) every key/token (?) in RAM, removing the need for the key cache, and providing an extremely fine grained pointer to the underlying row value data.
> Implement Lucene FST in for key index
> -------------------------------------
>
> Key: CASSANDRA-4324
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4324
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jason Rutherglen
> Assignee: Jason Rutherglen
> Priority: Minor
> Attachments: CASSANDRA-4324.patch, CASSANDRA-4324.patch, CASSANDRA-4324.patch, lucene-core-4.0-SNAPSHOT.jar
>
>
> The Lucene FST data structure offers a compact and fast system for indexing Cassandra keys. More keys may be loaded which in turn should seeks faster.
> * Update the IndexSummary class to make use of the Lucene FST, overriding the serialization mechanism.
> * Alter SSTableReader to make use of the FST seek mechanism
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira