You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "T Jake Luciani (JIRA)" <ji...@apache.org> on 2010/11/22 20:19:14 UTC
[jira] Commented: (CASSANDRA-1591) get_range_slices always returns
super columns that's been removed/restored, regardless of count value in
slicerange
[ https://issues.apache.org/jira/browse/CASSANDRA-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934563#action_12934563 ]
T Jake Luciani commented on CASSANDRA-1591:
-------------------------------------------
LGTM +1
> get_range_slices always returns super columns that's been removed/restored, regardless of count value in slicerange
> -------------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-1591
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1591
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.6
> Environment: CentOS 5.4, single Cassandra node
> Reporter: Jianing hu
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.6.9
>
> Attachments: 1591-0.6-reproduce.txt, 1591.txt, test.pl
>
>
> I'm seeing cases where the count in slicerange predicate is not respected. This is only happening for super columns. I'm running Cassandra 0.6.4 in a single node.
> Steps to reproduce, using the Keyspace1.Super1 CF:
> * insert three super columns, bar1 bar 2, and bar3, under the same key
> * delete bar1
> * insert bar1 again
> * run a get_range_slices on Super1, with start=bar1, finish=bar3, and count=1
> * I expected only bar1 to be returned, but both both bar1 and bar2 are returned. bar3 isn't, though. so count is somewhat respected.
> perl code to reproduce is attached
> when I tried the same test on a standard CF it worked. only super CF seem to have this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.