[ 
https://issues.apache.org/jira/browse/CASSANDRA-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Ellis resolved CASSANDRA-3645.
---------------------------------------

    Resolution: Duplicate

You're right, this is normal tombstone behavior.  (See CASSANDRA-2569 for an 
earlier example.)
                
> Can't delete row with cqlsh via row key
> ---------------------------------------
>
>                 Key: CASSANDRA-3645
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3645
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.6
>            Reporter: Oleksandr Shyshko
>              Labels: cql, cqlsh, delete
>
> This is probably not a bug, but standard tombstone/deletion behavior.
> Maybe it would be nice to have a built-in filter for tombstones, so they 
> won't appears in queries.
> Reproduce by:
> ==================================================
> cqlsh> CREATE KEYSPACE ss WITH strategy_class = 'SimpleStrategy' AND 
> strategy_options:replication_factor = 1;
> cqlsh> use ss;
> cqlsh:ss> create columnfamily users (name text primary key, pass text);
> cqlsh:ss> select * from users;
> cqlsh:ss> insert into users (name, pass) values ('john', 'secret');
> cqlsh:ss> select * from users;
>  name |   pass |
>  john | secret |
> cqlsh:ss> delete from users where name = 'john';
> cqlsh:ss> select * from users;
>  name |
>  john |
> cqlsh:ss>
> ==================================================
> Desired behavior:
> ==================================================
> cqlsh:ss> delete from users where name = 'john';
> cqlsh:ss> select * from users;
> cqlsh:ss>
> ==================================================

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to