[ https://issues.apache.org/jira/browse/CASSANDRA-7123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986036#comment-13986036 ]
Alex P commented on CASSANDRA-7123: ----------------------------------- Current: bq. Note however that the BATCH statement only allows UPDATE, INSERT and DELETE statements and is not a full analogue for SQL transactions. Suggested edit: {quote} Note that: 1. the BATCH statement only allows UPDATE, INSERT and DELETE statements 2. it is *not* a full analogue for SQL transactions 3. there is *no* guaranteed order of applying the operations (even for the same partition key). To achieve a particular ordering of operations you must specify timestamps. {quote} > BATCH documentation should be explicit about ordering guarantees > ---------------------------------------------------------------- > > Key: CASSANDRA-7123 > URL: https://issues.apache.org/jira/browse/CASSANDRA-7123 > Project: Cassandra > Issue Type: Task > Components: Documentation & website > Reporter: Tyler Hobbs > Assignee: Tyler Hobbs > Priority: Minor > > In the CQL3 [batch statement > documentation](http://cassandra.apache.org/doc/cql3/CQL.html#batchStmt) we > don't mention that there are no ordering guarantees, which can lead to > somewhat surprising behavior (CASSANDRA-6291). > We should also mention that you could specify timestamps in order to achieve > a particular ordering. -- This message was sent by Atlassian JIRA (v6.2#6252)