[
https://issues.apache.org/jira/browse/CASSANDRA-4283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13283538#comment-13283538
]
Sylvain Lebresne commented on CASSANDRA-4283:
---------------------------------------------
No, the problem is that '2012-06-06' is always translated as '2012-06-06
00:00:00', but when you ask for {{time > '2012-06-06'}} you clearly don't
expect to get something dating of the 6 June at midnigt and 1 minute. Or in
other words, '2012-06-06' means a time range, more than a precise timestamp,
which we don't handle.
> CQL3: dates are not handled correctly in slices
> ------------------------------------------------
>
> Key: CASSANDRA-4283
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4283
> Project: Cassandra
> Issue Type: Bug
> Components: API
> Affects Versions: 1.1.0
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: cql3
> Fix For: 1.1.2
>
>
> Our timestamp type allows to input timestamp as dates like '2012-06-06'.
> However, those don't work as expected in slice queries, as for instance:
> {noformat}
> SELECT * FROM timeline
> WHERE k = ...
> AND time > '2012-06-06'
> AND time <= '2012-06-09'
> {noformat}
> will return timestamps from '2012-06-06' and not those from '2012-06-09'. The
> reason being of course that we always translate a date the same way, using 0
> for whichever part is not precised.
> A reasonably simple fix could be to add a new fromString(String s, boolean
> gt) method to AbstractType that is used when the the string should be
> interpreted in an inequality (the boolean gt would then say which kind of
> inequality).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
