thanks. both of you.
Nicolas
Le 25 janv. 2013 à 19:05, Tyler Hobbs ty...@datastax.com a écrit :
On Fri, Jan 25, 2013 at 8:07 AM, Nicolas Lalevée nicolas.lale...@hibnet.org
wrote:
Just a quick question about the attributes exposed via JMX. I have some doc
[1] but it doesn't help about CF
Hi all,
When I delete some rowkeys programmatically I can see two rowkeys remains
in the column family. I think it is due to tombstones. Is there a way to
remove it when deleting rowkeys. Can I run compaction programmatically
after deletion? will it remove all these remaining rowkeys.
Thanks,
What is your gc_grace set to?
Are your findings before or after this time after the deletion?
From: Kasun Weranga kas...@wso2.commailto:kas...@wso2.com
Reply-To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org
Date: Saturday,
Make sure the timestamp on your delete is then timestamp of the data.
On Sat, Jan 26, 2013 at 1:33 PM, Kasun Weranga kas...@wso2.com wrote:
Hi all,
When I delete some rowkeys programmatically I can see two rowkeys remains
in the column family. I think it is due to tombstones. Is there a way
Although I've got to know Cassandra for quite a while, this question
only has occurred to me recently:
Why are the replica placement strategy and replica factors set at the
keyspace level?
Would setting them at the column family level offers more flexibility?
Is this because it's easier for
