cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-10784) ZonedDateTime as new CQL data type
Date Mon, 04 Apr 2016 18:07:25 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksey Yeschenko resolved CASSANDRA-10784.
-------------------------------------------
       Resolution: Not A Problem
    Fix Version/s:     (was: 3.x)

I agree with Carl and Robert here. Same behaviour can be emulated with a UDT, and being able
to do so - instead of adding native types for every possible case - is the reason for UDTs
existing in the first place. Closing as {{Not A Problem}}

> ZonedDateTime as new CQL data type
> ----------------------------------
>
>                 Key: CASSANDRA-10784
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10784
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: CQL, Documentation and Website
>            Reporter: ZhaoYang
>            Assignee: ZhaoYang
>
> For globalization, ZonedDateTime is very important. Timestamp is not enough and Zone
info should be included. So Cassandra should support ZonedDateTime as native data type and
ordering using ZonedDateTime's utc value.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message