Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 4 May 2015 20:42:06 +0000 (UTC)
From: "T Jake Luciani (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12826550.1430489161000.74139.1430772126936@Atlassian.JIRA>
In-Reply-To: <JIRA.12826550.1430489161000@Atlassian.JIRA>
References: <JIRA.12826550.1430489161000@Atlassian.JIRA>
 <JIRA.12826550.1430489161591@arcas>
Subject: [jira] [Commented] (CASSANDRA-9283) Deprecate unlogged batches
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/CASSANDRA-9283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14527248#comment-14527248 ] 

T Jake Luciani commented on CASSANDRA-9283:
-------------------------------------------

So we might have an issue with CASSANDRA-7351

If we remove UNLOGGED and COUNTER in 4.0 then internally we would make COUNTER mutations avoid the batchlog and just document that?

> Deprecate unlogged batches
> --------------------------
>
>                 Key: CASSANDRA-9283
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9283
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Jonathan Ellis
>            Assignee: T Jake Luciani
>             Fix For: 3.0
>
>
> Officially mark unlogged batches deprecated.
> Note that the main "good" use case for unlogged batches, of multiple updates in a single partition key, is "free" when done as a logged batch.  So really unlogged batches mainly serve as a honeypot to trick new users into abusing them in misguided bulk loading attempts.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)