[
https://issues.apache.org/jira/browse/CASSANDRA-11873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15336215#comment-15336215
]
Sylvain Lebresne commented on CASSANDRA-11873:
----------------------------------------------
bq. I understand the rational of the suggestions but I would be in favor of
keeping what I proposed.
I concur (and will note that we're really just following the [internal standard
for those unit|https://en.wikipedia.org/wiki/Second#SI_multiples], which
weigths more in my book than any particular database choices).
That said, I do agree that making the unit case-insensitive would be nice
(because most stuffs in CQL as case-insensitive, and because having the
difference been only base on the case is error prone). Which is why I would
personally suggest using {{mo}} for months (I guess you could alternatively
keep {{m}} for months and force {{min}} for {{minutes}}, but I think it's way
more common to abbreviate minutes than month (in life in general) so I think
using something slightly irregular for month is less surprising).
> 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)
