Dear Wiki user, You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.
The "API" page has been changed by JonathanEllis. The comment on this change is: update to explain that CL.ALL is supported for reads in 0.5. http://wiki.apache.org/cassandra/API?action=diff&rev1=34&rev2=35 -------------------------------------------------- ||`ANY`||(Coming in 0.6) Ensure that the write has been written to at least 1 node, including hinted recipients.|| ||`ONE`||Ensure that the write has been written to at least 1 node's commit log and memory table before responding to the client.|| ||`QUORUM`||Ensure that the write has been written to `<ReplicationFactor> / 2 + 1` nodes before responding to the client.|| - ||`ALL`||Ensure that the write is written to `<ReplicationFactor>` nodes before responding to the client.|| + ||`ALL`||Ensure that the write is written to all `<ReplicationFactor>` nodes before responding to the client. Any unresponsive nodes will fail the operation.|| ==== Read ==== @@ -46, +46 @@ ||`ANY`||Not supported. You probably want ONE instead.|| ||`ONE`||Will return the record returned by the first node to respond. A consistency check is always done in a background thread to fix any consistency issues when `ConsistencyLevel.ONE` is used. This means subsequent calls will have correct data even if the initial read gets an older value. (This is called `read repair`.)|| ||`QUORUM`||Will query all storage nodes and return the record with the most recent timestamp once it has at least a majority of replicas reported. Again, the remaining replicas will be checked in the background.|| - ||`ALL`||Not yet supported, but we plan to eventually.|| + ||`ALL`|Will query all storage nodes and return the record with the most recent timestamp once all nodes have replied. Any unresponsive nodes will fail the operation.|| === ColumnPath and ColumnParent ===
