Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 12 Aug 2014 04:21:11 +0000 (UTC)
From: "Jeremiah Jordan (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12733348.1407792853128.61111.1407817271873@arcas>
In-Reply-To: <JIRA.12733348.1407792853128@arcas>
References: <JIRA.12733348.1407792853128@arcas>
Subject: [jira] [Updated] (CASSANDRA-7750) Do not flush on truncate if
 "durable_writes" is false.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jeremiah Jordan updated CASSANDRA-7750:
---------------------------------------

    Attachment: 7750-2.1.txt
                7750-2.0.txt

Patches for 2.0 and 2.1 to put back the "just throw the memtables away" code if durable writes is false and auto snapshot is false.

> Do not flush on truncate if "durable_writes" is false.
> ------------------------------------------------------
>
>                 Key: CASSANDRA-7750
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7750
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Jeremiah Jordan
>            Assignee: Jeremiah Jordan
>            Priority: Minor
>             Fix For: 2.0.10, 2.1.1
>
>         Attachments: 7750-2.0.txt, 7750-2.1.txt
>
>
> CASSANDRA-7511 changed truncate so it will always flush to fix commit log issues.  If durable_writes is false, then there will not be able data in the commit log for the table, so we can safely just drop the memtables and not flush.


--
This message was sent by Atlassian JIRA
(v6.2#6252)