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 tuxracer69. http://wiki.apache.org/cassandra/API?action=diff&rev1=26&rev2=27 -------------------------------------------------- === get_slice === `list<ColumnOrSuperColumn> get_slice(keyspace, key, column_parent, predicate, consistency_level)` - Get the group of columns contained by `column_parent` (either a !ColumnFamily name or a !ColumnFamily/!SuperColumn name pair) specified by the given `predicate`. If no matching values are found, an empty list is returned. Note that the number of columns returned is limited to 100 as of [[http://issues.apache.org/jira/browse/CASSANDRA-262|0.4]]. This can be modified without too much effort in Cassandra.thift by modifying the SliceRange struct. After doing so, rerun thrift by doing something like: ''thrift --gen (your language) -o /tmp cassandra.thrift'' and then replace your languages official files (use locate to find them) with the new ones in the /tmp directory. + Get the group of columns contained by `column_parent` (either a `ColumnFamily` name or a `ColumnFamily/SuperColumn` name pair) specified by the given `predicate`. If no matching values are found, an empty list is returned. Note that the number of columns returned is limited to 100 as of [[http://issues.apache.org/jira/browse/CASSANDRA-262|0.4]]. This can be modified without too much effort in Cassandra.thift by modifying the SliceRange struct. After doing so, rerun thrift by doing something like: ''thrift --gen (your language) -o /tmp cassandra.thrift'' and then replace your languages official files (use locate to find them) with the new ones in the /tmp directory. === multiget === `map<string,ColumnOrSuperColumn> multiget(keyspace, keys, column_path, consistency_level)` @@ -118, +118 @@ 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. + === insert === `insert(keyspace, key, column_path, value, timestamp, consistency_level)`
