Hi Dmitriy, I have taken a look and found out that cassandra-cli output after UPDATE and INSERT operation is different, On first update it is update test SET value=null where id='1'; [default at test] list test; ------------------- RowKey: 1 On first insert [default at test] list test; ------------------- RowKey: 1 => (name=, value=, timestamp=1398166276501000) On Wed, Apr 23, 2014 at 8:56 AM, Dmitriy Ukhlov <dukhlov at mirantis.com>wrote: > Hello everyone! > > Today I'm faced with unexpected Cassandra behavior. Please keep in mind > that if you execute UPDATE query end set all fields to null (or empty > collections for collection type) it can delete your record, but also it can > only set values to null and keep record alive. It depends on how to record > was created: using insert query or update query. Please take a look at > reproduce steps here https://gist.github.com/dukhlov/11195881. > FYI: Cassandra 2.0.7 has been released. As we know there were some fixes > for condition operation and batch operations which are necessary for us. So > It would be nice to update magnetodb devstack to use Cassandra 2.0.7 > > -- > Best regards, > Dmitriy Ukhlov > Mirantis Inc. > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140423/ba2859a0/attachment.html>