cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9733) InsertUpdateIfCondition.testConditionalDelete is failing on trunk
Date Wed, 08 Jul 2015 07:57:05 GMT


Stefania commented on CASSANDRA-9733:

[~slebresne], as far as I can see the problem with this ticket and CASSANDRA-9721 is that
we don't filter out partitions that have only cell tombstones. For example:

execute("INSERT INTO %s (k, v1) VALUES (2, 2) USING TTL 1");
execute("SELECT * FROM %s WHERE k=2");

This code returns {{\[2, null\]}} but the existing tests are expecting no rows returned. Is
this a change in behavior or something you are already aware and was planning on doing? If
not, excluding rows without live data in {{SelectStatement.processPartition()}} fixes all
ttl dtests except for two (which have NPEs), whilst for the cas operations I'm guessing we
should change the {{RowCondition.appliesTo}} implementations to treat  a row without live
data as not existing. Is this correct and are there other places that might have the same
problem (e.g. Thrift)?

>  InsertUpdateIfCondition.testConditionalDelete is failing on trunk
> ------------------------------------------------------------------
>                 Key: CASSANDRA-9733
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Benjamin Lerer
>            Assignee: Stefania
>  {{InsertUpdateIfCondition.testConditionalDelete}} is failing on trunk. 
> It looks that it got unnoticed because cassci was not running the test due to the fact
that the class name does not contains {{Test}}. 

This message was sent by Atlassian JIRA

View raw message