Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <985981179.1260323058267.JavaMail.jira@brutus>
Date: Wed, 9 Dec 2009 01:44:18 +0000 (UTC)
From: "Jonathan Ellis (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Resolved: (CASSANDRA-347) disabling commitlog as alternative
 to binarymemtable?
In-Reply-To: <1554576087.1249526594791.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis resolved CASSANDRA-347.
--------------------------------------

    Resolution: Won't Fix
      Assignee:     (was: Jonathan Ellis)

Serialization really is a bottleneck...  I'm afraid binarymemtable isn't going anywhere :)

> disabling commitlog as alternative to binarymemtable?
> -----------------------------------------------------
>
>                 Key: CASSANDRA-347
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-347
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>         Attachments: 347.patch
>
>
> IMO it's worth seeing if we can do without BMt since it's a secondary code path that doesn't see much use.  so you'll get done with BMT, then nobody will really test it until the next big import job at which point little bugs will have crept in because it just doesn't get run much.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.