> It is mostly a bitmap index, generated from your struct so you don't have to write and maintain it yourself.
That explanation makes complete sense, because with this in mind, I can compare it to Apache Druid which does the same thing for data spilled onto S3.
Since this is immutable, you only had to solve "naming things", since the caches didn't need to be invalidated.
Druid is technically mutable, since it lets you mutate whole segments & then cache these bitmasks without having the original data in memory.
But if your dataset is already in memory, this is a neat implementation of an index and it should be faster than Roaring since you can skip the extra translation to the row-id that requires.
Druid uses Roaring - https://dl.acm.org/doi/10.1145/2938503.2938515