Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Apache Wiki <wikidiffs@apache.org>
To: cassandra-commits@incubator.apache.org
Date: Tue, 25 Aug 2009 04:14:35 -0000
Message-ID: <20090825041435.1878.99787@eos.apache.org>
Subject: [Cassandra Wiki] Update of "API" by JoeStump

Dear Wiki user,

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

The following page has been changed by JoeStump:
http://wiki.apache.org/cassandra/API

The comment on the change is:
Added notes on SliceRange

------------------------------------------------------------------------------
  == Overview ==
  
- The Cassandra Thrift API changed between 0.3 and 0.4. 
+ The Cassandra Thrift API changed between 0.3 and 0.4. Cassandra's client API is built entirely on top of Thrift. It should be noted that these documents mention default values, which are not supported in all of the languages that Thrift supports. 
+ 
+ '''WARNING:''' Some SQL/RDBMS terminology being used in this documentation for analogy purposes. They should be thought of as just that; analogies. There are few similarities between how data is managed in a traditional RDBMS and Cassandra. Please see DataModel for more information.
  
  == Terminology / Abbreviations ==
   Keyspace:: Contains multiple Column Families
@@ -37, +39 @@

  ||`QUORUM`||Will query all storage nodes and return the record that is prevailing in consistency. For instance, if `foo = 1` on nodes A and B, while `foo = 2` on node C then the prevailing consistency is `foo = 1`. A background thread will be fired off to fix consistency issues.||
  ||`ALL`||Not supported.||
  
+ === SliceRange ===
+ 
+ A slice range is a structure that stores basic range, ordering and limit information for a query that will return multiple keys. It could be thought of as Cassandra's version of `LIMIT` and `ORDER BY`.
+ 
+ ||'''Attribute'''||'''Type'''||'''Default'''||'''Required'''||'''Description'''||
+ ||`start`||`binary`||n/a||Y||The column name to start the slice with. This attribute is not required, though there is no default value, and can be safely set to `''`. Can be numerical or characters.||
+ ||`finish`||`binary`||n/a||Y||The column name to stop the slice at. This attribute is not required, though there is no default value, and can be safely set to `''`. Can be an integer or string.||
+ ||`reversed`||`bool`||`false`||N||Whether the results should be ordered in reversed order. Similar to `ORDER BY blah DESC` in MySQL.||
+ ||`count`||`integer`||`100`||N||How many keys to return. Similar to `LIMIT 100` in MySQL.||
+ 
+ === SlicePredicate ===
+