Yes, you are correct.

Best Regards,

倪项菲/ David Ni
Virtue Intelligent Network Ltd, co.
Add: 2003,20F No.35 Luojia creative city,Luoyu Road,Wuhan,HuBei
Mob: +86 13797007811|Tel: + 86 27 5024 2516

发件人: onmstester onmstester <>
发送时间: 2018年5月28日 14:33
收件人: user <>
主题: Fwd: Re: cassandra update vs insert + delete

How update is working underneath?
Does it create a new row (because i'm changing a column of partition key) and 
add a tombstone to the old row?

Sent using Zoho Mail<>

============ Forwarded message ============
From : Jonathan Haddad <<>>
To : <<>>
Date : Mon, 28 May 2018 00:07:36 +0430
Subject : Re: cassandra update vs insert + delete
============ Forwarded message ============

What is a “soft delete”?

My 2 cents, if you want to update some information just update it. There’s no 
need to overthink it.

Batches are good if they’re constrained to a single partition, not so hot 

On Sun, May 27, 2018 at 8:19 AM Rahul Singh 
<<>> wrote:

Jon Haddad
twitter: rustyrazorblade
Deletes create tombstones — not really something to consider. Better to add / 
update or insert data and do a soft delete on old data and apply a TTL to 
remove it at a future time.

Rahul Singh<>

Anant Corporation

On May 27, 2018, 5:36 AM -0400, onmstester onmstester 
<<>>, wrote:

I want to load all rows from many partitions and change a column value in each 
row, which of following ways is better concerning disk space and performance?
1. create a update statement for every row and batch update for each partitions
2. create an insert statement for every row and batch insert for each 
partition, then run a single statement to delete the whole old partition

Thanks in advance

Sent using Zoho Mail<>

Reply via email to