cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-4324) Implement Lucene FST in for key index
Date Mon, 29 Apr 2013 15:40:16 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13644583#comment-13644583
] 

Jonathan Ellis commented on CASSANDRA-4324:
-------------------------------------------

My point is that keys routed to a given node will be effectively a random subset of the keys
in use (under RP/M3P), so unlike the tokens I don't think it's clear at all that they will
be well-compressible by FST. 
                
> 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

Mime
View raw message