Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DFDDB11E23 for ; Wed, 25 Jun 2014 12:46:25 +0000 (UTC) Received: (qmail 7777 invoked by uid 500); 25 Jun 2014 12:46:25 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 7739 invoked by uid 500); 25 Jun 2014 12:46:25 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 7727 invoked by uid 99); 25 Jun 2014 12:46:25 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jun 2014 12:46:25 +0000 Date: Wed, 25 Jun 2014 12:46:25 +0000 (UTC) From: "Benedict (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-7443) SSTable Pluggability v2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-7443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14043399#comment-14043399 ] Benedict commented on CASSANDRA-7443: ------------------------------------- We will have to dice up CFS somewhat no doubt, yes - as soon as we start messing with CC and Memtables, CFS is in the mix too. With some of these changes and compaction etc., I'm sort of tempted to wait until we have a new storage API (which may follow this ticket)... we need to try and do this piecemeal as it is going to be a difficult project. Let's make it minimally abstract, then iterate from there :) Specifically for compaction, you can already drop a custom compaction strategy (which permits, e.g., turning it off), but we probably don't want to reimplement LCS/STCS etc. for each storage engine that needs them. > SSTable Pluggability v2 > ----------------------- > > Key: CASSANDRA-7443 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7443 > Project: Cassandra > Issue Type: Bug > Components: Core > Reporter: T Jake Luciani > Assignee: T Jake Luciani > Fix For: 3.0 > > > 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.2#6252)