It was removed because the "right" way to do this is to page by last-column-seen, which can take advantage of the per-row column index. Offset cannot.
On Wed, Jul 6, 2011 at 3:04 AM, Boris Yen <yulin...@gmail.com> wrote: > Hi, > > It seems it was implemented before. However, due to Cassandra-286, it was > removed. I was wondering if it is possible to put it back. Because computing > the offset on the client side should be less efficient than do it on the > server side. > > I am thinking this might be possible to achieve by tweaking both the > CassandraServer.multigetSliceInternal and CassandraServer.getSlice. Let us > assume there is one extra attribute called "offset" inside SliceRange > object. When the "offset" attribute exists in the SliceRange, the read > command should be create like "new SliceFromReadCommand(keyspace, key, > column_parent, range.start, range.finish, range.reversed, > range.count+range.offset)". And then, the only thing left to do is to make > the CassandraServer.getSlice be aware of the "offset", based on offset it > should be able to return the right fragment of data. > > Boris > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
