[
https://issues.apache.org/jira/browse/CASSANDRA-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416388#comment-13416388
]
Jason Rutherglen commented on CASSANDRA-4324:
---------------------------------------------
Nice that's a huge win! That's for the MD5 encoded keys?
{quote}DecoratedKeys stored inside current IndexSummary are actually accessed
from various places, and FST version will lack those information, you may need
to figure out the alternative way to preserve current functionality{quote}
Interesting, what is the information? Why are there two keys stored in
DecoratedKey?
FST supports range like scans, however I am not exactly sure how that part
works. We probably want to restructure the API to make it abstract for both
implementations?
> 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
> Fix For: 1.2
>
> 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:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
