[
https://issues.apache.org/jira/browse/CASSANDRA-9229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519391#comment-14519391
]
Robert Stupp commented on CASSANDRA-9229:
-----------------------------------------
bq. stored internally in UTC but the way it is output is not clearly defined
All we can do is to return it in UTC. The rest is purely a client issue.
bq. converting from a {{UUIDTimestampType}} to a {{TimeType}}
For option #1, I'd propose UTC as the base. The server timezone could vary -
especially in global multi-DC setups. So server timezone is not a good option.
But I prefer the 2nd option (_do not provide that type of function_, {{toTime}}
or the other way round: date+time to timestamp). Time from a timestamp is
relative to the time zone. Time zones (as well as currencies) change regularly.
I don’t think we want to add the burden to ourself or to the user to keep
timezone definitions up-to-date on *all* nodes.
> Add functions to convert timeuuid to date or time
> -------------------------------------------------
>
> Key: CASSANDRA-9229
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9229
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Michaël Figuière
> Assignee: Benjamin Lerer
> Labels: cql, doc-impacting
> Fix For: 3.0
>
> Attachments: CASSANDRA-9229.txt
>
>
> As CASSANDRA-7523 brings the {{date}} and {{time}} native types to Cassandra,
> it would be useful to add builtin function to convert {{timeuuid}} to these
> two new types, just like {{dateOf()}} is doing for timestamps.
> {{timeOf()}} would extract the time component from a {{timeuuid}}. Example
> use case could be at insert time with for instance {{timeOf(now())}}, as well
> as at read time to compare the time component of a {{timeuuid}} column in a
> {{WHERE}} clause.
> The use cases would be similar for {{date}} but the solution is slightly less
> obvious, as in a perfect world we would want {{dateOf()}} to convert to
> {{date}} and {{timestampOf()}} for {{timestamp}}, unfortunately {{dateOf()}}
> already exist and convert to a {{timestamp}}, not a {{date}}. Making this
> change would break many existing CQL queries which is not acceptable.
> Therefore we could use a different name formatting logic such as {{toDate}}
> or {{dateFrom}}. We could then also consider using this new name convention
> for the 3 dates related types and just have {{dateOf}} becoming a deprecated
> alias.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
