I would avoid taking away a feature even if it works in narrow set of use-cases. I would instead suggest -
1. Leave it disabled by default. 2. Detect when Row Cache has a low hit rate and warn the operator to turn it off. Cassandra should ideally detect this and do it automatically. 3. Move to Caffeine instead of OHC. I would suggest having this as the middle ground. > On Dec 14, 2023, at 4:41 PM, Mick Semb Wever <m...@apache.org> wrote: > > > >> >> 3. Deprecate the row cache entirely in either 5.0 or 5.1 and remove it in a >> later release > > > > I'm for deprecating and removing it. > It constantly trips users up and just causes pain. > > Yes it works in some very narrow situations, but those situations often > change over time and again just bites the user. Without the row-cache I > believe users would quickly find other, more suitable and lasting, solutions.
