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: Re-added my changes that Arin deleted. ------------------------------------------------------------------------------ ||`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 === +
