and read repair will fix the data?
If not, how cassandra prevent from this?
-邮件原件-
发件人: Jonathan Ellis [mailto:jbel...@gmail.com]
发送时间: 2011年3月10日 10:19
收件人: user@cassandra.apache.org
主题: Re: understanding tombstones
On Wed, Mar 9, 2011 at 4:54 PM, Jeffrey Wang jw...@palantir.com wrote:
insert
: understanding tombstones
On Wed, Mar 9, 2011 at 4:54 PM, Jeffrey Wang jw...@palantir.com wrote:
insert row X with timestamp T
delete row X with timestamp T+1
force flush + compaction
insert row X with timestamp T
My understanding is that the tombstone created by the delete (and row X
Hey all,
I was wondering if this is the expected behavior of deletes (0.7.0). Let's say
I have a 1-node cluster with a single CF which has gc_grace_seconds = 0. The
following sequence of operations happens (in the given order):
insert row X with timestamp T
delete row X with timestamp T+1
On Wed, Mar 9, 2011 at 4:54 PM, Jeffrey Wang jw...@palantir.com wrote:
insert row X with timestamp T
delete row X with timestamp T+1
force flush + compaction
insert row X with timestamp T
My understanding is that the tombstone created by the delete (and row X)
will disappear with the flush
Yup. https://issues.apache.org/jira/browse/CASSANDRA-2305
-Jeffrey
-Original Message-
From: Jonathan Ellis [mailto:jbel...@gmail.com]
Sent: Wednesday, March 09, 2011 6:19 PM
To: user@cassandra.apache.org
Subject: Re: understanding tombstones
On Wed, Mar 9, 2011 at 4:54 PM, Jeffrey Wang
