cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4738) Improve CQL3 batchlog support
Date Mon, 01 Oct 2012 16:15:07 GMT

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

Sylvain Lebresne updated CASSANDRA-4738:
----------------------------------------

    Attachment: 4738.txt
    
> Improve CQL3 batchlog support 
> ------------------------------
>
>                 Key: CASSANDRA-4738
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4738
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>            Priority: Minor
>             Fix For: 1.2.0 beta 2
>
>         Attachments: 4738.txt
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message