[
https://issues.apache.org/jira/browse/CASSANDRA-11873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314784#comment-15314784
]
Tyler Hobbs commented on CASSANDRA-11873:
-----------------------------------------
Overall, I like the design for the Duration type.
I'm a little hesitant to use {{µs}} instead of {{us}}, just because {{u}} is
much easier to work with.
Since this is a new type, we should go ahead and make the serialization format
byte-order comparable by storing it as an unsigned 64bit int centered at 2^63,
similar to {{DateType}}.
Can you add duration entries to the existing tests in {{JsonTest}}?
{{ViewFilteringTest}} and {{ViewSchemaTest}} also have a couple of tests that
are supposed to cover all types.
> 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)
