[
https://issues.apache.org/jira/browse/CASSANDRA-11873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451669#comment-15451669
]
Benjamin Lerer commented on CASSANDRA-11873:
--------------------------------------------
I realised that there is 2 problem with my proposal:
# it is not always possible to properly order the duration as they rely on the
context. For example, which is the greater {{1mo}} or {{30d}} (same question
for {{1y}} or {{365d}}). I think it is the main reason why Oracle splitted
their interval type into 2 types (year to month) and (day to fraction of
second).
# having the type Byte-ordered (CASSANDRA-6936) will require to store useless
data if a part of the duration is not used.
Due to these problems I will be in favor of using 2 types but I would like to
know your opinion.
> 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)
