[ https://issues.apache.org/jira/browse/CASSANDRA-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169256#comment-14169256 ]
Marcus Eriksson commented on CASSANDRA-7443: -------------------------------------------- bq. the iterator must still return data in the same order regardless of the format. right, but I'm imagining (perhaps prematurely) that some sstable formats could be compacted in a much more efficient way if we have a way of scanning sstables without that requirement during compaction > SSTable Pluggability v2 > ----------------------- > > Key: CASSANDRA-7443 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7443 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: T Jake Luciani > Assignee: T Jake Luciani > Fix For: 3.0 > > Attachments: 7443-refactor-v1.txt, 7443-testformat-v1.txt > > > As part of a wider effort to improve the performance of our storage engine we > will need to support basic pluggability of the SSTable reader/writer. We > primarily need this to support the current SSTable format and new SSTable > format in the same version. This will also let us encapsulate the changes in > a single layer vs forcing the whole engine to change at once. > We previously discussed how to accomplish this in CASSANDRA-3067 > -- This message was sent by Atlassian JIRA (v6.3.4#6332)