Soft delete = logical delete - which is an update.
An update doesnt create a tombstone . It appends to the sstable,and when they
are compacted, the latest write is what is seen as the definitive data.
A tombstone by definition is an update which tells C* to remove the value that
was there before, but doesn’t do it immediately .
On May 28, 2018, 2:32 AM -0400, onmstester onmstester ,
wrote:
> 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
> > otherwise.
> >
> >
> > On Sun, May 27, 2018 at 8:19 AM Rahul Singh
> > wrote:
> >
> > --
> > Jon Haddad
> > http://www.rustyrazorblade.com
> > 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
> > > rahul.si...@anant.us
> > >
> > > Anant Corporation
> > >
> > > On May 27, 2018, 5:36 AM -0400, onmstester onmstester
> > > , wrote:
> > >
> > > > Hi
> > > > 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
> > > >
>
>