Return-Path: Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: (qmail 43531 invoked from network); 24 Jan 2011 19:21:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Jan 2011 19:21:13 -0000 Received: (qmail 53876 invoked by uid 500); 24 Jan 2011 19:21:12 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 53835 invoked by uid 500); 24 Jan 2011 19:21:12 -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 53827 invoked by uid 99); 24 Jan 2011 19:21:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jan 2011 19:21:12 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Jan 2011 19:21:10 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id p0OJKmsi018531 for ; Mon, 24 Jan 2011 19:20:48 GMT Message-ID: <9239376.164621295896848802.JavaMail.jira@thor> Date: Mon, 24 Jan 2011 14:20:48 -0500 (EST) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Subject: [jira] Created: (CASSANDRA-2043) remove memtable throughput configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org remove memtable throughput configuration ---------------------------------------- Key: CASSANDRA-2043 URL: https://issues.apache.org/jira/browse/CASSANDRA-2043 Project: Cassandra Issue Type: New Feature Components: Core Reporter: Jonathan Ellis Assignee: Jon Hermes Fix For: 0.8 Now that we can set memtable thresholds on a per-CF basis, having two sizing thresholds is more confusing than helpful, especially for new users who see the throughput threshold and think that it accurately represents how much memory a memtable will use -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.