[
https://issues.apache.org/jira/browse/CASSANDRA-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107828#comment-13107828
]
Jonathan Ellis commented on CASSANDRA-3228:
-------------------------------------------
bq. I also disagree on the idea of putting new features into CQL only
A primary motivation for CQL is that it's too much effort to keep feature
parity across RPC-based clients. (Case in point: the ruby gem, which is
actively maintained as these things go, STILL does not have 2ary index query
support.)
So while we do plan to support "legacy" RPC indefinitely I do think it's valid
to say "new features go into CQL."
> Add new range scan with clock
> -----------------------------
>
> Key: CASSANDRA-3228
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3228
> 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: http://www.atlassian.com/software/jira
