cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Lerer (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11873) Add duration type
Date Fri, 17 Jun 2016 13:47:05 GMT


Benjamin Lerer commented on CASSANDRA-11873:

bq. What CQL type has nanosecond resolution?

{{Time}} has nanosecond resolution. By consequence I strongly believe that we need microseconds
and nanoseconds support.

1. Change "us" to "u" to be consistent with InfluxDB, and to keep the abbreviations consistently
to 1 letter.
2. Change the "ns" to "n" to keep all the abbreviations consistently to one letter. 

I think that looking at what other are doing is a good thing but I do not think that we should
bother following exactly what they are doing if they are the only one doing it.
In my opinion, we should keep {{ms}} for milliseconds as we will have to find something less
natural otherwise. In this case it seems to me that we can also keep {{us}} and {{ns}}.

I understand the rational of the suggestions but I would be in favor of keeping what I proposed.

> 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