Ok, I've found the answer, this is just for the record.
The 100K limit is not related to 2nd index but to tombstone itself. It has
been introduced recently (C* 2.0.2)
The JIRA : https://issues.apache.org/jira/browse/CASSANDRA-6117
The commit:
https://github.com/jbellis/cassandra/commit/4ac18ae
Sorry, my finger slipped on "enter"
So as I said,
http://www.datastax.com/documentation/cql/3.1/cql/ddl/ddl_when_use_index_c.html
*Problems using an index on a frequently updated or deleted column*
Cassandra stores tombstones in the index until the tombstone limit reaches
*100K* cells. After exc
Hello
I've read the documentation about secondary index and among the use-cases
to avoid, there is the case of frequenty updated/deleted columns:
