[
https://issues.apache.org/jira/browse/CASSANDRA-6951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13951597#comment-13951597
]
Aleksey Yeschenko commented on CASSANDRA-6951:
----------------------------------------------
CASSANDRA-6782 is the change (this is intentional, not a bug).
> update query deletes instead of update, upgraded to 2.0.6
> ---------------------------------------------------------
>
> Key: CASSANDRA-6951
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6951
> Project: Cassandra
> Issue Type: Bug
> Environment: ubuntu 12.04 on ec2
> Reporter: Pardeep Singh
>
> I'm showing two examples below to show what happens. I'm using update, but
> technically it's an insert. This worked in the previous version, which I
> don't remember but it was 1.2+
> cqlsh:tagloom> update user_timeline set d=null WHERE uid='aa' and pid='aa';
> cqlsh:tagloom> select * from user_timeline where uid='aa' limit 4;
> (0 rows)
> cqlsh:tagloom> update user_timeline set d='a' WHERE uid='aa' and pid='aa';
> cqlsh:tagloom> select * from user_timeline where uid='aa' limit 4;
> uid | pid | d
> -----+-----+---
> aa | aa | a
> (1 rows)
> I run it again:
> cqlsh:tagloom> update user_timeline set d=null WHERE uid='aa' and pid='aa';
> cqlsh:tagloom> select * from user_timeline where uid='aa' limit 4;
> (0 rows)
> Seems like it's deleting the row. Was there a change that made the above
> results possible or is it a bug?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
