Hi team, I am currently doing some tests/research about upsert functionality and understood that I data with high cardinality for primary keys can use much heap space for storing upsert metadata. But my question is about storing this metadata off-heap(on disk, in KV-store or somewhere else). I found different threads that this work is currently in progress now and want to know on what stage is it? Maybe there are some estimations when it would be done? And is there some design document about it? I will be grateful for any information 🙂

We are evaluating off-heap implementations atm. cc: @Kartik Khare

@Kartik Khare any information?)

Hi, it is currently WIP. We are finalizing the implementation at the moment. I will share the design doc soon with the community as well as the PR. (Approx time 2-3 weeks)

Hello team -- any update on this ?