You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "ruilonghe1988 (JIRA)" <ji...@apache.org> on 2016/11/30 14:40:58 UTC
[jira] [Created] (CASSANDRA-12977) column expire to null can still
be retrieved using not null value in where clause
ruilonghe1988 created CASSANDRA-12977:
-----------------------------------------
Summary: column expire to null can still be retrieved using not null value in where clause
Key: CASSANDRA-12977
URL: https://issues.apache.org/jira/browse/CASSANDRA-12977
Project: Cassandra
Issue Type: Bug
Components: CQL
Environment: cql 5.0.1
cassandra 2.1.5
Reporter: ruilonghe1988
Attachments: attatchment.txt
1. first create table:
create table device_share(
device_id text primary key,
share_status text,
share_expire boolean
);
CREATE INDEX expireIndex ON device_share (share_expire);
create index statusIndex ON device_share (share_status);
2.insert a new record:
insert into device_share(device_id,share_status,share_expire) values ('d1','ready',false);
3. update the share_expire value to fase with ttl 20
update device_share using ttl 20 set share_expire = false where device_id = 'd1';
4.after 20 seconds, can retrieve the record with condition where share_expire = false, but the record in the console show the share_expire is null.
cqlsh:test> select * from device_share where device_id ='d1' and share_status='ready' and share_expire = false allow filtering;
device_id | share_expire | share_status
-----------+--------------+--------------
d1 | null | ready
is this a bug?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)