[
https://issues.apache.org/jira/browse/CASSANDRA-10701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15006894#comment-15006894
]
Jon Haddad commented on CASSANDRA-10701:
----------------------------------------
There's a few references here: https://cassandra.apache.org/doc/cql3/CQL.html
Instead of:
{quote}By default, all operations in the batch are performed atomically. See
the notes on UNLOGGED for more details.{quote}
how about:
{quote}By default, all operations in the batch are performed as LOGGED, to
ensure all mutations eventually complete. See the notes on UNLOGGED for more
details.{quote}
Replace:
{quote}By default, Cassandra uses a batch log to ensure all operations in a
batch are applied atomically. {quote}
With:
{quote}By default, Cassandra uses a batch log to ensure all operations
eventually complete. {quote}
Replace:
{quote}There is a performance penalty for batch atomicity when a batch spans
multiple partitions. If you do not want to incur this penalty, you can tell
Cassandra to skip the batchlog with the UNLOGGED option. If the UNLOGGED option
is used, operations are only atomic within a single partition.{quote}
With:
{quote}There is a performance penalty for batch logging when a batch spans
multiple partitions. If you do not want to incur this penalty, you can tell
Cassandra to skip the batchlog with the UNLOGGED option.{quote}
> stop referring to batches as atomic
> -----------------------------------
>
> Key: CASSANDRA-10701
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10701
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jon Haddad
> Priority: Minor
>
> We still refer to logged batches as atomic, we should remove those references.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
