More info: the RDBMS based db gets changed by writers in a vicinity of 40-50% of all data e.g. 100GB a week. The indexes can be defrugged, which is both expensive and time consuming. Many indexes become quickly out of date.
Not sure what you mean in retrospect to consistency against indexes. I doubt there is room for bugs, this is a "by design" application behaviour. Regards, Arthur ---- Original Message ---- From: Hannu Kröger <hkro...@gmail.com> To: user <user@cassandra.apache.org> Sent: Sun, Sep 28, 2014 11:30 am Subject: Re: Indexes Fragmentation Hi, I think more information is needed before this question can be answered. In many cases you manage the indexes by yourself. If that breaks, then you have a consistency problem or a bug in your own code. Consistency is tunable (trade off with performance and availability) and bugs can be fixed. In any case, if you can shed a bit light on the use case, then it would be easier to answer your question. Hannu ---------- Forwarded message ---------- From: Arthur Zubarev <arthur.zuba...@aol.com> Date: 2014-09-28 17:55 GMT+03:00 Subject: Indexes Fragmentation To: user@cassandra.apache.org Hi all: A client on a RDBMS faces quick index fragmentations, statistics become inaccurate. Many within 4 hours (fast updates + writes, but mostly updates). I am looking into replacing the RDBMS with Cassandra. Will I face the same issue with indexes with Cassandra? Thank you! Regards, Arthur
