> Can you please elaborate on the specials of truncate?
I think ed was talking about this config setting in 1.2
https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L484
> It works, only sometimes it silently fails (1 in 400 runs of the truncate,
> actually).
The data is left in p
Hi,
I have JNA (cassandra only complains about obsolete version - Obsolete
version of JNA present; unable to read errno. Upgrade to JNA 3.2.7 or later
- I have stock centos version 3.2.4).
Usage of separate CFs for each test run is difficult to set up.
Can you please elaborate on the specials of
If you do not have JNA truncate has to fork an 'ln -s'' command for the
snapshots. I think that makes it un-predicatable. Truncate has its own
timeout value now (separate from the other timeouts). If possible I think
it is better to make each test use it's own CF and avoid truncate entirely.
On T
Hi,
I use C* 1.2.3 and CQL3.
I integrated cassandra into our testing environment. In order to make the
tests repeatable I truncate all the tables that need to be empty before the
test run via ssh session to the host cassandra runs on and by running cqlsh
where I issue the truncate.
It works, onl
