[ https://issues.apache.org/jira/browse/CASSANDRA-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107607#comment-13107607 ]
Jonathan Ellis commented on CASSANDRA-3228: ------------------------------------------- Zero interest in adding Thrift RPC calls at this point. It *might* be okay to do this in CQL, although keeping timestamp as an implementation detail of conflict resolution makes a lot of sense to me. > 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