[
https://issues.apache.org/jira/browse/CASSANDRA-6395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lorcan Coyle updated CASSANDRA-6395:
------------------------------------
Description:
Currently it is impossible to query for dates with the minTimeuuid and
maxTimeuuid functions with sub-second accuracy from cqlsh because the parser
doesn't recognise dates formatted at that granularity (e.g., 2013-09-30
22:19:06.591). By adding the following ISO8601 patterns to TimestampSerializer
this functionality is unlocked:
"yyyy-MM-dd HH:mm:ss.SSS",
"yyyy-MM-dd HH:mm:ss.SSSZ",
"yyyy-MM-dd'T'HH:mm:ss.SSS",
"yyyy-MM-dd'T'HH:mm:ss.SSSZ".
I submitted this as a pull-request on the github mirror
(https://github.com/apache/cassandra/pull/23), which I'll close now. I'll
submit a patch to address this here.
was:
Currently it is impossible to query for dates with sub-second accuracy from
cqlsh because the parser doesn't recognise dates formatted at that granularity
(e.g., 2013-09-30 22:19:06.591). By adding the following ISO8601 patterns to
TimestampSerializer this functionality is unlocked:
"yyyy-MM-dd HH:mm:ss.SSS",
"yyyy-MM-dd HH:mm:ss.SSSZ",
"yyyy-MM-dd'T'HH:mm:ss.SSS",
"yyyy-MM-dd'T'HH:mm:ss.SSSZ".
I submitted this as a pull-request on the github mirror
(https://github.com/apache/cassandra/pull/23), which I'll close now. I'll
submit a patch to address this here.
> Add the ability to query by TimeUUIDs with milisecond granularity
> -----------------------------------------------------------------
>
> Key: CASSANDRA-6395
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6395
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Lorcan Coyle
> Priority: Minor
> Labels: easyfix, patch
> Fix For: 2.0.1
>
>
> Currently it is impossible to query for dates with the minTimeuuid and
> maxTimeuuid functions with sub-second accuracy from cqlsh because the parser
> doesn't recognise dates formatted at that granularity (e.g., 2013-09-30
> 22:19:06.591). By adding the following ISO8601 patterns to
> TimestampSerializer this functionality is unlocked:
> "yyyy-MM-dd HH:mm:ss.SSS",
> "yyyy-MM-dd HH:mm:ss.SSSZ",
> "yyyy-MM-dd'T'HH:mm:ss.SSS",
> "yyyy-MM-dd'T'HH:mm:ss.SSSZ".
> I submitted this as a pull-request on the github mirror
> (https://github.com/apache/cassandra/pull/23), which I'll close now. I'll
> submit a patch to address this here.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
