Hi!
If I use sstableloader to load data to a cluster, and the source
sstables contain some columns where the TTL has expired, i.e. the
sstable has not yet been compacted - will those entries be properly
removed on the destination side?
Thanks,
\EF
Hi!
I'm looking into moving some data from one Cassandra cluster to another,
both of them running Cassandra 1.2.13 (or maybe some later 1.2 version
if that helps me avoid some fatal bug). Sstableloader will probably be
the right thing for me, and given the size of my tables, I will want to
run the
Hi,
I'm trying this cql against cassandra 2.0.9:
BEGIN BATCH
INSERT INTO cqlengine_test_lwt.test_if_not_exists_model (id, count,
text) VALUES (1, 8, '123');
INSERT INTO cqlengine_test_lwt.test_if_not_exists_model (id, count,
text) VALUES (1, 9, '111');
APPLY BATCH;
In thi
You're running into funny results due to the way CQL3 handles statements in
batches. Read this:
https://github.com/doanduyhai/Achilles/wiki/Batch-Mode#statements-ordering
There is already a JIRA opened but according to the developers this is the
expected behavior.
In your example, largest value
wow, that's really interesting. Thanks for saving my time.
On 16 August 2014 20:56, DuyHai Doan wrote:
> You're running into funny results due to the way CQL3 handles statements
> in batches. Read this:
> https://github.com/doanduyhai/Achilles/wiki/Batch-Mode#statements-ordering
>
> There is al
