Adrien Grand

It's still relevant but I'm not comfortable with the fact that it's a bit fragile. I'll close for now and think more about it.

@salvatore-campagna If I read the source code correctly, the `_ignored` field has an inverted index, so it already provides us with index statistics (see the `org.apache.lucene.index.Terms` class): - `getDocCount()`: number...

I have mixed feelings about this proposal. One the one end we like enriching our indexes to be able to provide more context. On the other hand, it ends up...

Apologies @javanna, but after looking more at your changes, I'm getting worried that this change is harder than I had anticipated. I was optimistically hoping that never returning null PointValues...

We could use `IndexGeonames`, which has a `batchAddDocuments` boolean value aimed at checking exactly this.

I think there was an alternative proposal of tracking recall over time instead of checking that hits are strictly the same.

Lucene implements this idea via the common grams filter: https://lucene.apache.org/core/9_7_0/analysis/common/org/apache/lucene/analysis/commongrams/package-summary.html. That said it's not especially easy to integrate with Lucene's query parsers, and I don't recall seeing anyone using it....

Sorry, I no longer have time to maintain this project.

Thanks for looking. Unfortunately, the case I'm most interested in is when `storeOffsets` is false and there are no payloads, since this is the default. :)

It looks like `writeGroupVInt` has room for improvement. Can we improve it by making it look a bit more like the read logic?