http://www.datastax.com/dev/blog/datastax-java-driver-3-0-0-released#unset-values
"For Protocol V3 or below, all variables in a statement must be bound. With Protocol V4, variables can be left "unset", in which case they will be ignored server-side (no tombstones will be generated)." From: Ralf Steppacher [mailto:ralf.viva...@gmail.com] Sent: Thursday, March 24, 2016 11:19 AM To: user@cassandra.apache.org Subject: Re: Large number of tombstones without delete or update 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<mailto: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
