cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Cassandra Wiki] Update of "Counters" by JorisvanderWel
Date Thu, 03 Nov 2011 21:19:37 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.

The "Counters" page has been changed by JorisvanderWel:

Added a small clarification to the Counter limitations (checked with rev 1197311)

    * If a write fails unexpectedly (timeout or loss of connection to the coordinator node)
the client will not know if the operation has been performed. A retry can result in an over
count [[|CASSANDRA-2495]].
    * Counter removal is intrinsically limited. For instance, if you issue very quickly the
sequence "increment, remove, increment" it is possible for the removal to be lost (if for
some reason the remove happens to be the last received messages). Hence, removal of counters
is provided for definitive removal only, that is when the deleted counter is not increment
afterwards. Note that if you need to reset a counter, you can read its ''value'' and insert
+   * `CounterColumnType` may only be set in the `default_validation_class`. A column family
either contains only counters, or no counters at all.
  == Further reading ==
  See [[|CASSANDRA-1072]] and especially
the [[|design
doc]] for further information about how this works internally (but note that some of the limitation
fixed in these technical documents have been fixed since then, for instance all consistency
level '''are''' supported, for both reads and writes).

View raw message