cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Evans <>
Subject Re: Bug regarding removing and retrieving entire supercolumn.
Date Sun, 04 Apr 2010 22:06:35 GMT
On Sat, 2010-04-03 at 02:55 +0200, Arash Bazrafshan wrote:
> Think I got a bug in Cassandra. Do you also think it's a bug?
> It should be noted that I experience this bug when using cassandra
> through thrift's php api (the low-level one generated by thrift, not
> some high-level from the cassandra wiki).
> It happens when i insert a supercolumn (with a single column "bar")
> under key "foo", and then delete the supercolumn (under the same key).
> After that if I insert the same supercolumn (with the same column)
> under key "foo" then I'm not able to retrieve it (the entire
> supercolumn).
> However I am able to retrieve the single column "bar" within the
> supercolumn.
> So If I try to retrieve the entire supercolumn then I get
> "notfoundexception", but if I wanna fetch the single column "bar"
> within the supercolumn, then that's fine.

See if you can replicate this using the bin/cassandra-cli. I've attached
a file with the equivalent commands, you can pipe it to stdin on the
command line (i.e. bin/cassandra-cli --host localhost <


FWIW, I wasn't able to replicate this (

Eric Evans

View raw message