You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by buddhasystem <po...@bnl.gov> on 2011/03/18 21:12:33 UTC
Undead rows after nodetool compact
This has been discussed once, but I don't remember the outcome. I insert a
row and then delete the key immediately. I then run nodetool compact. In
cassanra-cli, "list cf" still return 1 empty row. This is not a showstopper
but damn unpretty. Is there a way to make deleted rows go, immediately?
--
View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Undead-rows-after-nodetool-compact-tp6186021p6186021.html
Sent from the cassandra-user@incubator.apache.org mailing list archive at Nabble.com.
Re: Undead rows after nodetool compact
Posted by Tyler Hobbs <ty...@datastax.com>.
http://wiki.apache.org/cassandra/FAQ#range_ghosts
On Fri, Mar 18, 2011 at 3:12 PM, buddhasystem <po...@bnl.gov> wrote:
> This has been discussed once, but I don't remember the outcome. I insert a
> row and then delete the key immediately. I then run nodetool compact. In
> cassanra-cli, "list cf" still return 1 empty row. This is not a showstopper
> but damn unpretty. Is there a way to make deleted rows go, immediately?
>
>
> --
> View this message in context:
> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Undead-rows-after-nodetool-compact-tp6186021p6186021.html
> Sent from the cassandra-user@incubator.apache.org mailing list archive at
> Nabble.com.
>
--
Tyler Hobbs
Software Engineer, DataStax <http://datastax.com/>
Maintainer of the pycassa <http://github.com/pycassa/pycassa> Cassandra
Python client library