What is the reason for the tombstone for a brand new insert? Do the fields get written as a whole (both nulls and non-nulls?
I understand the rationale for tombstones for deletes and updates but it does not make sense for an insert (I am trying to make sense of it). I understand Cassandra writes the record without first checking its existence but wouldn't the whole set of fields including values to null out be applied as one single operation? Thank you, Henry On Wed, Mar 23, 2016 at 5:47 PM, Eric Stevens <migh...@gmail.com> wrote: > In addition to writing null values acting as tombstones, also INSERTing a > collection (or UPDATE where you set the collection rather than append to > it) are also operations which will create tombstones. > > On Wed, Mar 23, 2016 at 12:09 PM Robert Coli <rc...@eventbrite.com> wrote: > >> On Wed, Mar 23, 2016 at 9:50 AM, Ralf Steppacher <ralf.viva...@gmail.com> >> wrote: >> >>> How come I end up with that large a number of tombstones? >>> >> >> Are you inserting NULLs? >> >> =Rob >> >> >
