You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/01/26 00:09:13 UTC

[jira] [Commented] (CASSANDRA-3672) Cassandra returns 0 columns instead 2 in get_slice

    [ https://issues.apache.org/jira/browse/CASSANDRA-3672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563141#comment-13563141 ] 

Jonathan Ellis commented on CASSANDRA-3672:
-------------------------------------------

Yes, you do need to make sure insert timestamps are greater than the delete's, since the tombstone will win a tie.
                
> Cassandra returns 0 columns instead 2 in get_slice
> --------------------------------------------------
>
>                 Key: CASSANDRA-3672
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3672
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Win32
>            Reporter: Michael Morozov
>            Priority: Minor
>         Attachments: CassandraTest.java, CassandraTestWA.java
>
>
> Cassandra returns 0 columns instead N in get_slice call.
> But if we will make a pause in the thread after remove a key, column list size is ok.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira