Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of sylvain@datastax.com designates
 209.85.214.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <12032_1335169200_4F9510B0_12032_4431_1_AEE40020481AB74EAADC798FC2BC7C4A01B0AF3CE43C@THSONEA01CMS03P.one.grp>
References: 
 <CAAQs3wt_ckameEwweK-gaqJDH5B7UxbBgThLh-imdN6dkEq=AQ@mail.gmail.com>
	<3FFCCFCC-5394-4919-8A0B-D5302789B700@gmail.com>
	<12032_1335169200_4F9510B0_12032_4431_1_AEE40020481AB74EAADC798FC2BC7C4A01B0AF3CE43C@THSONEA01CMS03P.one.grp>
Date: Mon, 23 Apr 2012 10:56:18 +0200
Message-ID: 
 <CAKkz8Q1qdfHWmNEgA4DVcc6_5gnMRGTduS5xsSQTwaf2AhYBQQ@mail.gmail.com>
Subject: Re: question about updates internal work in case of cache
From: Sylvain Lebresne <sylvain@datastax.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Apr 23, 2012 at 10:19 AM, DE VITO Dominique
<dominique.devito@thalesgroup.com> wrote:
> Hi,
>
>
>
> Let's suppose a column (name+value) is cached in memory, with timestamp T.
>
>
>
> 1) An update, for this column, arrives with exactly the *same* timestamp,
> and the *same* value.
>
> Is the commitlog updated ?
>
>
>
> 2) An update, for this column, arrives with a timestamp < T.
>
> Is the commitlog updated ?
>

Yes to both, the commit log is always updated. In fact, the commit log
insertion is done in parallel and independently with in-memory updates
(which include caches updates).

--
Sylvain

>
>
> Thanks for your help.
>
>
>
> Regards,
>
> Dominique
>
>