cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11873) Add duration type
Date Tue, 14 Jun 2016 21:47:30 GMT

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

Tyler Hobbs commented on CASSANDRA-11873:
-----------------------------------------

{quote}
Will you be able to bind to the duration? As in:
session.prepare("SELECT * FROM myTable WHERE pkey=5 AND clustCol > now() - ?")
or
session.prepare("SELECT * FROM myTable WHERE pkey=5 AND clustCol > now() - ?h")
{quote}

You will be able to use the first example you listed.  The unit suffix is part of the value,
so the second example wouldn't work.

> Add duration type
> -----------------
>
>                 Key: CASSANDRA-11873
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11873
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: Benjamin Lerer
>            Assignee: Benjamin Lerer
>              Labels: client-impacting, doc-impacting
>             Fix For: 3.x
>
>
> For CASSANDRA-11871 or to allow queries with {{WHERE}} clause like:
> {{... WHERE reading_time < now() - 2h}}, we need to support some duration type.
> In my opinion, it should be represented internally as a number of microseconds.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message