[
https://issues.apache.org/jira/browse/CASSANDRA-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Ellis updated CASSANDRA-4324:
--------------------------------------
Reviewer: (was: yukim)
Does CASSANDRA-5506 make this obsolete? ISTM that the savings here can only
come from the Token, since the keys themselves will not be ordered
appropriately. (That is: CASSANDRA-5506 orders the keys by token, but only
stores the underlying key byte[], and regenerates the token when necessary.)
> 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
