[
https://issues.apache.org/jira/browse/CASSANDRA-11873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15552969#comment-15552969
]
Benjamin Lerer commented on CASSANDRA-11873:
--------------------------------------------
bq. 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?
In my opinion having some checks will be probably less confusing for the user.
With the current binary representation used for duration, the order will be
completely random.
I have pushed some new branches for 3.X and trunk with some fixes for all the
problems that you raised.
||Branch||utests||dtests||
|[3.X|https://github.com/blerer/cassandra/tree/11873-3.X]|[3.X|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11873-3.X-testall/]|[3.X|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11873-3.X-dtest/]|
|[trunk|https://github.com/blerer/cassandra/tree/11873-trunk]|[trunk|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11873-trunk-testall/]|[trunk|http://cassci.datastax.com/view/Dev/view/blerer/job/blerer-11873-trunk-dtest/]|
bq. We will also need to add "duration" to the python driver's reserved
keywords in {{cassandra/metadata.py}}.
I did not tackle that part but I thought that there will be more work to do on
the python driver side.
> 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)
