[
https://issues.apache.org/jira/browse/CASSANDRA-9229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14519690#comment-14519690
]
Joshua McKenzie commented on CASSANDRA-9229:
--------------------------------------------
Do we even need to take time zone into account when converting into a "nanos
since midnight" Time type? It makes intuitive / logical sense to me that the
conversion would be *relative to the original source input*, which in this case
is UTC. Along with that, the Time type has no conception of time zone which
strongly implies it does not take that into consideration on conversions and
can be clearly documented.
If you want a Time relative to your local time zone that's on you in client
application-space.
> 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)
