You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Alex P (JIRA)" <ji...@apache.org> on 2014/05/01 19:07:16 UTC
[jira] [Comment Edited] (CASSANDRA-7123) BATCH documentation should
be explicit about ordering guarantees
[ https://issues.apache.org/jira/browse/CASSANDRA-7123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986769#comment-13986769 ]
Alex P edited comment on CASSANDRA-7123 at 5/1/14 5:06 PM:
-----------------------------------------------------------
lgtm. (the fact that we hint the cause of ordering without giving details that might be misused is imo the right approach)
was (Author: alexyz):
lgtm
> 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
> Attachments: 7123-v2.txt, 7123.txt
>
>
> 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)