[
https://issues.apache.org/jira/browse/CASSANDRA-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13107713#comment-13107713
]
Sylvain Lebresne commented on CASSANDRA-3228:
---------------------------------------------
For what it's worth, I think that *if* we wanted to add that to thrift, it
would make more sense as a new optional field of SlicePredicate (and internally
that would be part of the column filtering code anyway).
I also disagree on the idea of putting new features into CQL only. Or rather, I
think that if adding something to Thrift can be done easily without breaking
backward compatibility (which I believe would likely be the case here), then we
should do it. Or otherwise we should say that thrift is going deprecated, but I
don't think this is the plan so far.
> 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
