[
https://issues.apache.org/jira/browse/CASSANDRA-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924595#action_12924595
]
Gary Dusbabek edited comment on CASSANDRA-1652 at 10/25/10 11:57 AM:
---------------------------------------------------------------------
Confirmed broken in 0.6. The root of the problem is that
BytesType.compare("c1", "c") == 1, which is correct.
EDIT: semantically, specifying start==finish can only ever imply one column
(equality), right?
was (Author: gdusbabek):
Confirmed broken in 0.6. The root of the problem is that
BytesType.compare("c1", "c") == 1, which is correct.
> slice range is not inclusive when start and finish are the same
> ---------------------------------------------------------------
>
> Key: CASSANDRA-1652
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1652
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 0.6
> Reporter: Brandon Williams
> Assignee: Gary Dusbabek
> Fix For: 0.7.0
>
> Attachments: inclusive_failure_test.txt
>
>
> When the same start and finish are specified, the range returned is empty,
> rather than being inclusive.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
