using 0.7 latest from trunk as of few minutes ago. 1 client, 1 node
i have the scenario where i want to drop a column family and recreate it
- unit testing for instance, is a good reason you may want to do this
(always start fresh).
the problem i observe is that if i do the following:
1 -
On Tue, Sep 7, 2010 at 3:55 PM, B. Todd Burruss bburr...@real.com wrote:
using 0.7 latest from trunk as of few minutes ago. 1 client, 1 node
i have the scenario where i want to drop a column family and recreate it -
unit testing for instance, is a good reason you may want to do this (always
On Tue, Sep 7, 2010 at 5:10 PM, Jonathan Ellis jbel...@gmail.com wrote:
On Tue, Sep 7, 2010 at 3:55 PM, B. Todd Burruss bburr...@real.com wrote:
using 0.7 latest from trunk as of few minutes ago. 1 client, 1 node
i have the scenario where i want to drop a column family and recreate it -
unit
https://issues.apache.org/jira/browse/CASSANDRA-1477
comments below
On 09/07/2010 02:10 PM, Jonathan Ellis wrote:
On Tue, Sep 7, 2010 at 3:55 PM, B. Todd Burrussbburr...@real.com wrote:
using 0.7 latest from trunk as of few minutes ago. 1 client, 1 node
i have the scenario where i want
5 secs isn't enough for me, 10 is good. i haven't tried any other
values as i can get around this through another manner.
On 09/07/2010 02:24 PM, Edward Capriolo wrote:
On Tue, Sep 7, 2010 at 5:10 PM, Jonathan Ellisjbel...@gmail.com wrote:
On Tue, Sep 7, 2010 at 3:55 PM, B. Todd
On Tue, Sep 7, 2010 at 4:29 PM, B. Todd Burruss bburr...@real.com wrote:
if you are referring to R, W, N - i am aware, but i have a one node cluster,
with R=W=N = 1. single threaded test app. any column manipulations would
be immediate because R+WN, so i assume the same for column family
truncate doesn't change schema, it just drops the data associated with
it. so it's a different beast from either normal writes or schema
change.
truncate will wait for each node to response, and send a
TimedOutException if any do not.
On Tue, Sep 7, 2010 at 5:42 PM, B. Todd Burruss
