[CASSANDRA-4738] Improve CQL3 batchlog support

• Type: Improvement
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 1.2.0 beta 2
• Assignee: Sylvain Lebresne
• Reporter: Sylvain Lebresne

Authors

Sylvain Lebresne

Reviewers

Jonathan Ellis

• Created: 01/Oct/12 16:13
• Updated: 16/Apr/19 09:32
• Resolved: 02/Oct/12 16:38

Description

This is a follow-up on CASSANDRA-4545. We've made batch be atomic by default, however it is actually possible for normal inserts to not be atomic by default thanks to the support of the IN notation.

I don't think this is very coherent so I suggest the two following changes:

• make sure normal inserts/deletes are always atomic ("logged")
• make sure we use mutate (rather than mutateAtomically) if there is only one mutation (i.e. use the batch log in normal inserts/deletes only if there is an IN).

And if people really want to do "unlogged" insert with IN, they can put the insert inside an unlogged batch.