The semantics of "null" is encoded at the protocol side, all you can do is trying to tweak at client side to handle "null" semantics correctly with regards to your business
On Mon, Jun 23, 2014 at 8:34 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Sat, Jun 21, 2014 at 11:17 AM, Kevin Burton <bur...@spinn3r.com> wrote: > >> AH! that makes sense then… so second time around, when you write null, >> you're actually writing a tombstone, then during the next compaction, less >> data will be stored and the value will be removed. >> >> Makes sense! Not sure why I didn't realize that immediately :-P >> > > You're not the only one... > > http://www.edwardcapriolo.com/roller/edwardcapriolo/entry/wait_say_what > > It's a little weird, because columns with no values is a pretty tried and > true Cassandra technique. Adding values can significantly increase space on > disk, often for no win.. > > =Rob > >
