thanks all for the pointers. let' me see if I can put the sequences of event together ....
1.2 people mis-understand/mis-use row cache, that cassandra cached the entire row of data even if you are only looking for small subset of the row data. e.g select single_column from a_wide_row_table will result in entire row cached even if you are only interested in one single column of a row. 2.0 and because of potential misuse of heap memory, Cassandra 2.0 remove heap cache, and only support off-heap cache, which has a side effect that write will invalidate the row cache(my original question) 2.1 the coming 2.1 Cassandra will offer true cache by query, so the cached data will be much more efficient even for wide rows(it cached what it needs). do I get it right? for the new 2.1 row caching, is it still true that a write or update to the row will still invalidate the cached row ? On Tue, Apr 29, 2014 at 3:00 PM, Robert Coli <rc...@eventbrite.com> wrote: > On Tue, Apr 29, 2014 at 1:53 PM, Brian Lam <y2k...@gmail.com> wrote: > >> Are these issues 'resolved' only in 2.0 or later release? >> >> What about 1.2 version? >> > > As I understand it : > > 1.2 version has the on-heap row cache and off-heap row cache. It does not > have the new "partition" cache. > 2.0 version has only the off-heap row cache. It does not have the on-heap > row cache or the new "partition" cache. > 2.1 version has the new "partition" cache. > > In summary, you probably don't want to use any of these half-baked, > immature internal row/etc. "caches" unless you are very, very certain that > you have an ideal case for them. > > =Rob >
