Yes, that is correct.—
Sent from Mailbox
On Sat, Jun 21, 2014 at 8:18 PM, Kevin Burton 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
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
On Sat, Jun 21, 2014 at 6:20 AM, D
With CQL3 semantics, setting a column to "null" means deleting it (e.g.
creating a tombstone column). It is different from having a "non-null
column name and a null cell".
On Sat, Jun 21, 2014 at 12:17 PM, Jens Rantil wrote:
> Hi Kevin,
>
> I can explain as I've understood things. Experts, let
I think the latency is expressed in micro-second
On Sat, Jun 21, 2014 at 3:32 AM, Senhua Huang
wrote:
> Hi all,
>
> I have a quick question on the unit of the latency in the output of
> cassandra-stress: is it milli-second or second? I cannot find the answer in
> the documentation:
>
> http:/
Hi Kevin,
I can explain as I've understood things. Experts, let me know if I got this
wrong! Here you go:
Simplified, when using a CQL-created table the underlying clustering key
for your columns is actually (YOUR_CLUSTERING_KEY, columnname). Because of
this, setting YOURCOLUMN to null, simply de
