[Cassandra Wiki] Update of "API" by gdusbabek

[Apache Wiki <wi...@apache.org>]

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 gdusbabek.
The comment on this change is: Documented trunk (0.6) status of CL.ANY and get_key_range.
http://wiki.apache.org/cassandra/API?action=diff&rev1=33&rev2=34

--------------------------------------------------

  
  ||'''Level'''||'''Behavior'''||
  ||`ZERO`||Ensure nothing. A write happens asynchronously in background||
+ ||`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.||
@@ -42, +43 @@

  
  ||'''Level'''||'''Behavior'''||
  ||`ZERO`||Not supported, because it doesn't make sense.||
+ ||`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.||
@@ -128, +130 @@

  
  Returns a list of keys starting with `start`, ending with `finish` (both inclusive), and at most `count` long.  The empty string ("") can be used as a sentinel value to get the first/last existing key.  (The semantics are similar to the corresponding components of `SliceRange`.)  This method is only allowed when using an order-preserving partitioner.
  
- ''Note'': `get_key_range`'s design is kind of fundamentally broken, so we're deprecating it in favor of `get_range_slice` starting in 0.5. In trunk (0.5beta) `get_range_slice` should be used instead.
+ ''Note'': `get_key_range`'s design is kind of fundamentally broken, so we're deprecating it in favor of `get_range_slice` starting in 0.5. `get_range_slice` should be used instead.  In trunk (0.6) this method has been removed entirely.
  
  
  === insert ===