It’s pretty clear to me that the only thing that gets put into the caches are
the top N rows.
https://github.com/apache/cassandra/blob/0db88242c66d3a7193a9ad836f9a515b3ac7f9fa/src/java/org/apache/cassandra/db/SinglePartitionReadCommand.java#L523
It may fetch more, but it doesn’t cache it. It
> On 12 Mar 2018, at 14:45, Rahul Singh wrote:
>
> 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
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
Hi,
My goal is to make sure that I understand functionality correctly and that the
documentation is accurate.
The question in other words: Is the documentation or the comment in the code
wrong (or inaccurate).
Hannu
> On 12 Mar 2018, at 13:00, Rahul Singh
What’s the goal? How big are your partitions , size in MB and in rows?
--
Rahul Singh
rahul.si...@anant.us
Anant Corporation
On Mar 12, 2018, 6:37 AM -0400, Hannu Kröger , wrote:
> Anyone?
>
> > On 4 Mar 2018, at 20:45, Hannu Kröger wrote:
> >
> > Hello,
>
Anyone?
> On 4 Mar 2018, at 20:45, Hannu Kröger wrote:
>
> Hello,
>
> I am trying to verify and understand fully the functionality of row cache in
> Cassandra.
>
> I have been using mainly two different sources for information:
>
Hello,
I am trying to verify and understand fully the functionality of row cache in
Cassandra.
I have been using mainly two different sources for information: