I may be wrong, but what I’ve read and used in the past assumes that the “first” N rows are cached and the clustering key design is how I change what N rows are put into memory. Looking at the code, it seems that’s the case.
The language of the comment basically says that it holds in cache what satisfies the query if and only if it’s the head of the partition, if not it fetches it and saves it - I dont interpret it differently from what I have seen in the documentation. -- Rahul Singh rahul.si...@anant.us Anant Corporation On Mar 12, 2018, 7:13 AM -0400, Hannu Kröger <hkro...@gmail.com>, wrote: > > rows_per_partition
