[
https://issues.apache.org/jira/browse/CASSANDRA-10784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15063564#comment-15063564
]
ZhaoYang commented on CASSANDRA-10784:
--------------------------------------
[~snazy] Hi Robert, thanks for the reply. I understand it's very bad to let
Cassandra synchronized time zone info and these country-related regulations may
change over time.
Converting ZonedDateTime data into 2 column( 1 utc column and 1 zone column)
can be done by client side logic. but It will be more convenient if cassandra
can get the ZonedDateTime inserted by users and sorted on utc value. Cassandra
doesn't need to know about reference data. only store utc and zone internally.
BTW, what's the reason to implement a datastax.LocalDate instead of using
java.LocalDate. Both use ISO-8601. Is it similarly because of changes between
java releases.
> 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
> Fix For: 3.x
>
>
> 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)
