I was planning to change my column from nonfrozen to frozen. I would like to know if there are any guidelines for updating the frozen column with respect to tombstone generation. In some blogs it is written that updating a frozen column generates the row tombstone. Is it correct? I would like to understand the concept of tombstone generation with respect to frozen column update.

I am new to Scylla, and I'm looking to setup a proper Backup & Restore solution. I've just tested running nodetool snapshot -t my_backup, and see that what it does is create a snapshot folder caled my_backup, inside each keyspace & table folder. This causes a few limitations in my view: 1) I can't easily save the backups on another server, in case this specific server dies 2) I can't easily restore a backup on another server (e.g. as a daily snapshot for production support purposes/tests) **How do DBAs normally store backups in another server and restore a whole database into another server ?** -- Another issue I noticed is that nodetool listsnapshots doesn't seem to mention the snapshot creation date in the output. So I don't seem to be able to find a way to purge old snapshots. **How do I "delete snapshots older than 10 days" or "keep last 3 backups", for example?**

I have created the following table CONSISTENCY LOCAL_QUORUM; drop keyspace if exists cycling; CREATE KEYSPACE IF NOT EXISTS cycling WITH REPLICATION = { 'class' : 'SimpleStrategy', 'replication_factor' : 3 } and durable_writes = true; CREATE TABLE IF NOT EXISTS cycling.rider ( rider_id int PRIMARY KEY, rider_name list, rider_name2 frozen> ); Do the following sequence of batch operations CONSISTENCY LOCAL_QUORUM; BEGIN BATCH UPDATE cycling.rider SET rider_name = ['a2'], rider_name2 = ['b2'] WHERE rider_id = 100; UPDATE cycling.rider SET rider_name = ['a3'], rider_name2 = ['b3'] WHERE rider_id = 100; APPLY BATCH; I get merged data in my list (rider_name) select * from cycling.rider; rider_id | rider_name | rider_name2 ----------+--------------+------------- 100 | ['a2', 'a3'] | ['b3'] Do you know why? I was expecting rider_id | rider_name | rider_name2 ----------+--------------+------------- 100 | ['a3'] | ['b3']