I did some more tests with my particular schema/message structure: A null text field inside a UDT instance does NOT yield tombstones. A null map does NOT yield tombstones. A null text field does yield tombstones.
Ralf > On 24.03.2016, at 09:42, Ralf Steppacher <ralf.viva...@gmail.com> wrote: > > I can confirm that if I send JSON messages that always cover all schema > fields the tombstone issue is not reported by Cassandra. > So, is there a way to work around this issue other than to always populate > every column of the schema with every insert? That would be a pain in the > backside, really. > > Why would C* not warn about the excessive number of tombstones if queried > from cqlsh? > > > Thanks! > Ralf > > > >> On 23.03.2016, at 19:09, Robert Coli <rc...@eventbrite.com >> <mailto:rc...@eventbrite.com>> wrote: >> >> On Wed, Mar 23, 2016 at 9:50 AM, Ralf Steppacher <ralf.viva...@gmail.com >> <mailto:ralf.viva...@gmail.com>> wrote: >> How come I end up with that large a number of tombstones? >> >> Are you inserting NULLs? >> >> =Rob >> >
