Issue created.
Will attach debug logs asap
CASSANDRA-4670<https://issues.apache.org/jira/browse/CASSANDRA-4670>
Von: aaron morton [mailto:aa...@thelastpickle.com]
Gesendet: Montag, 17. September 2012 03:46
An: user@cassandra.apache.org
Betreff: Re: secondery indexes TTL - strange issues
index_type : 0},
> {column_name : '0003--1000--',
> validation_class : BytesType,
> index_name : 'ebi_eventtypeIndex',
> index_type : 0}]
> and compression_options={sstable_compression:SnappyCompressor,
> chunk_length_kb:64};
bi_eventtypeIndex',
index_type : 0}]
and compression_options={sstable_compression:SnappyCompressor,
chunk_length_kb:64};
Von: aaron morton [mailto:aa...@thelastpickle.com]
Gesendet: Freitag, 14. September 2012 10:46
An: user@cassandra.apache.org
Betreff: Re: secondery indexes TTL - strange
> INFO [CompactionExecutor:181] 2012-09-13 12:58:37,443 CompactionTask.java
> (line
> 221) Compacted to
> [/var/lib/cassandra/data/Eventstore/EventsByItem/Eventstore-E
> ventsByItem.ebi_eventtypeIndex-he-10-Data.db,]. 78,623,000 to 373,348 (~0%
> of o
> riginal) bytes for 83 keys at 0.000280MB/
Hi,
we have been running a system on Cassandra 0.7 heavily relying on secondary
indexes for columns with TTL.
This has been working like a charm, but we are trying hard to move forward with
Cassandra and are struggling at that point:
When we put our data into a new cluster (any 1.1.x version -
