[
https://issues.apache.org/jira/browse/CASSANDRA-7523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14056150#comment-14056150
]
Sylvain Lebresne commented on CASSANDRA-7523:
---------------------------------------------
One small concern is the native protocol. As there will be no specific cause
for those, they will be sent as "custom" types (i.e the full AbstractType class
name will be sent). It's not a huge deal, clients can special case based on the
class name, but maybe we could shove codes for those in the protocol v3 before
2.1 final is released (that is, we'll ask drivers to support those types in v3
even though we might really support them only in say 2.1.1). I don't know.
> add date and time types
> -----------------------
>
> Key: CASSANDRA-7523
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7523
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Reporter: Jonathan Ellis
> Assignee: Joshua McKenzie
> Priority: Minor
> Fix For: 2.0.10
>
>
> http://www.postgresql.org/docs/9.1/static/datatype-datetime.html
> (we already have timestamp; interval is out of scope for now, and see
> CASSANDRA-6350 for discussion on timestamp-with-time-zone. but date/time
> should be pretty easy to add.)
--
This message was sent by Atlassian JIRA
(v6.2#6252)
