cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3228) Add new range scan with clock
Date Mon, 19 Sep 2011 15:16:08 GMT


Sylvain Lebresne commented on CASSANDRA-3228:

But it's the point of backward compatibility, isn't it ? That the ruby gem don't have 2ary
index support rather prove that you can have a client without need full support of all the
features. It's another point totally to say no client can get the feature.

Again, I'm all for saying that we don't add anything that is not backward compatible, because
the cons (the almost impossibility for clients to do rolling upgrades) of making backward
incompatible changes outweigh any pros of adding a new feature. But not adding backward compatible
changes just means we're not even trying. Or that we actively want to bias user towards switching
to CQL, de facto deprecating the thrift API (deprecation being != removal). If so, I don't
remember that discussion, not in those terms at least :) 

> Add new range scan with clock
> -----------------------------
>                 Key: CASSANDRA-3228
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: 0.8.5
>            Reporter: Todd Nine
>            Priority: Minor
> Currently, it is not possible to specify minimum clock time on columns when performing
range scans.  In some situations, such as custom migration or batch processing, it would be
helpful to allow the client to specify a minimum clock time.  This would only return columns
with a clock value >= the specified. 
> I.E
> range scan (rowKey, startVal, endVal, revered, min clock)

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message