cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9283) Deprecate unlogged batches
Date Mon, 04 May 2015 20:58:07 GMT

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

Aleksey Yeschenko commented on CASSANDRA-9283:
----------------------------------------------

COUNTER mutations already avoid batchlog. This doesn't really change anything wrt CASSANDRA-7351.

Question is, whether or not we should drop COUNTER and UNLOGGED *syntax* and only leave BEGIN
BATCH syntax available for everything.

But that's not a question for today. Today we should just formally note in the spec that this
stuff is deprecated, and emit warning on the server side.

> 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)

Mime
View raw message