cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11873) Add duration type
Date Wed, 05 Oct 2016 16:24:20 GMT


Tyler Hobbs commented on CASSANDRA-11873:

It also occurred to me that set items and map keys are also sorted, and would need to be handled
or rejected.  Perhaps we should just specify that duration types are sorted by their binary
representation and not try to restrict them from being used anywhere that could result in
an ordering?  I feel like that might bite/surprise a few people, but it might also be the
most sane option.  If we do this, we should make the docs very clear about it.

On a related note, I think we should also clearly document how equality operations work for
durations, so that, for example, nobody expects {{1d}} and {{86400s}} to be equal.

> Add duration type
> -----------------
>                 Key: CASSANDRA-11873
>                 URL:
>             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

View raw message