You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/01/25 22:41:14 UTC

[jira] [Commented] (CASSANDRA-3228) Add new range scan with clock

    [ https://issues.apache.org/jira/browse/CASSANDRA-3228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563068#comment-13563068 ] 

Jonathan Ellis commented on CASSANDRA-3228:
-------------------------------------------

I don't think treating timestamp as a first-class (pseudo)column value this way is a good fit for Cassandra.
                
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira