Actually each column in a row has the same TTL, so I guess that will not cause
fragmentation...?
Anyway - any feedback on the questions in my previous mail?
From: Nate McCall [n...@thelastpickle.com]
Sent: Wednesday, August 21, 2013 8:26 PM
To: Cassandra Users
Subj
Well, these tables are somewhat similar to a 'cache' - we insert rows, then
leave them for a week using TTL (usually untouched, read only), and then we
need to compact them away. If I understand correctly, they should not be
affected by the below issue...
The question is rather if the setup is c
Hi,
I ran upgradesstables as part of the Cassandra upgrade, before issuing the CQL
alter command.
According to the docs, SizeTieredCompactionStrategy is fine (that is what I
used, and plan on continue using), and automatic tombstone compaction is
available for it:
http://www.datastax.com/docume
Hi,
After upgrading from 1.0 to 1.2, I wanted to make use of the automatic
tombstone compaction feature, so using CQL3 I issued:
ALTER TABLE versions WITH compaction = {'class' :
'SizeTieredCompactionStrategy', 'min_threshold' : 4, 'max_threshold' : 32,
'tombstone_compaction_interval' : 1, 'to
All right - we will probably proceed with the upgrade then, thanks for the help!
From: Nate McCall [mailto:n...@thelastpickle.com]
Sent: 19. august 2013 17:31
To: user@cassandra.apache.org
Subject: Re: fromIndex > toIndex in Cassandra 1.2.5
Meant to put this in up top, but if you are upgrading, i
That's good news.
But the thing is - I don't have the client exception, so I cannot tell if this
is what really happens.
I checked the logs for each of our client applications, but no exceptions, so
the only other possibility is that someone manually runs a bad query. It's
possible, but still a
Hi,
We are upgrading our 1.0 Cassandra installation to 1.2 (via 1.1), and had
Cassandra 1.2.5 running in test for a while.
Everything seems fine except that exceptions like below come sporadically,
without correlating with anything else. They *seem* to come during work hours,
so it can be that
