Ok, thanks.
On Fri, May 6, 2011 at 8:32 PM, Jonathan Ellis wrote:
> Column objects are treated as immutable so it's quite likely you'll
> get back the same Columns (and buffers) if your query hits a local
> memtable. This was possible in 0.7.0 as well.
>
It's funny as this was a unit test that
Column objects are treated as immutable so it's quite likely you'll
get back the same Columns (and buffers) if your query hits a local
memtable. This was possible in 0.7.0 as well.
(This only applies to the StorageProxy interface, if you're going over
Thrift it will do a copy over the network.)
Row cache is still disabled by default.
AFAIK in general you should not move the position on any buffer in cassandra or
take ownership of them.
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 6 May 2011, at 07:34, Paul Loy wrote:
> H
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 'p
