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 keteracel@gmail.com designates
 209.85.220.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=i74QFYGQ66LkL9pDoDJqwoX3NSl2AMUduh8sv4rO4u7aZnE1Ns+/iS8xg2kHT5RJSO
         lc8p29E/+1z4aL30yXtPAA/noaf5JVXrdzorpWCC2EYv9nL0yjn27LXlFbWVyEJ0UFYc
         P+SEap2Cr+s2n4B+pgNcfLHtT5GNu7bpOFa04=
MIME-Version: 1.0
Date: Thu, 5 May 2011 12:34:41 -0700
Message-ID: <BANLkTikZuXgeUeg=9e87ZJL8=U-Wx8==jg@mail.gmail.com>
Subject: caching change between 0.7.0 and 0.7.5
From: Paul Loy <keteracel@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=20cf3071d088f5214504a28c7695

--20cf3071d088f5214504a28c7695
Content-Type: text/plain; charset=ISO-8859-1

Hi all,

so I just updated Cassandra from 0.7.0 to 0.7.5. I embed Cassandra in my app
and use StorageProxy for querying.

In one of my unit tests I write a column to Cassandra and then read it out
again twice in quick succession. The second time I now get the same
ByteBuffer (i.e. same id - same 'physical' HeapByteBuffer) as the first
call. But as I have consumed this, the position == capacity.

I have fixed this in my code by simply using ByteBuffer#duplicate, however
I'm concerned that caching may have changed between versions and want to
know what the implications of that change may be.

So my questions are:

1) is the Row Cache now enabled by default?
2) or is there now some other form of caching that is causing this to happen
that I should be aware of?

We're pretty close to deploying into production when we came across a
critical bug in 0.7.0 (infinite loop in HashMap) which means we have to
upgrade but I'm concerned that the changes mean our load/stress tests will
not be valid so just need some info to put my mind at ease!

Many thanks,

Paul.

-- 
---------------------------------------------
Paul Loy
paul@keteracel.com
http://uk.linkedin.com/in/paulloy

--20cf3071d088f5214504a28c7695
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi all,<br><br>so I just updated Cassandra from 0.7.0 to 0.7.5. I embed Cas=
sandra in my app and use StorageProxy for querying.<br><br>In one of my uni=
t tests I write a column to Cassandra and then read it out again twice in q=
uick succession. The second time I now get the same ByteBuffer (i.e. same i=
d - same &#39;physical&#39; HeapByteBuffer) as the first call. But as I hav=
e consumed this, the position =3D=3D capacity.<br>
<br>I have fixed this in my code by simply using ByteBuffer#duplicate, howe=
ver I&#39;m concerned that caching may have changed between versions and wa=
nt to know what the implications of that change may be.<br><br>So my questi=
ons are:<br>
<br>1) is the Row Cache now enabled by default?<br>2) or is there now some =
other form of caching that is causing this to happen that I should be aware=
 of?<br><br>We&#39;re pretty close to deploying into production when we cam=
e across a critical bug in 0.7.0 (infinite loop in HashMap) which means we =
have to upgrade but I&#39;m concerned that the changes mean our load/stress=
 tests will not be valid so just need some info to put my mind at ease!<br>
<br>Many thanks,<br><br>Paul.<br clear=3D"all"><br>-- <br>-----------------=
----------------------------<br>Paul Loy<br><a href=3D"mailto:paul@keterace=
l.com" target=3D"_blank">paul@keteracel.com</a><br><a href=3D"http://uk.lin=
kedin.com/in/paulloy" title=3D"View public profile" name=3D"SafeHtmlFilter_=
webProfileURL" target=3D"_blank">http://uk.linkedin.com/in/paulloy</a><br>


--20cf3071d088f5214504a28c7695--