Adrien Grand

Does it actually improve readability? I know some Java projects like to be very granular in how they organize packages, but I've come to like Lucene's relatively flat package structure,...

Thinking out loud: I'd like queries to remain as close to value classes as possible, just describing an information need. I believe that the change you're suggesting would require storing...

> A general framework on IndexSearcher sounds nice, but it's hard to generalize with just this one use case? Can it be something like IndexWriter's InfoStream, but for search? Or...

The high-level change makes sense to me. We've used this trick to encode 3 21-bit integers in a 64-bit long in the past, it makes sense to me that it's...

Disabling concurrent merging for terms, norms and doc values until we figure out how to make it compatible with SortingCodecReader sounds good to me.

I wonder if this use-case would be better served by something like Elasticsearch's shard request cache. The cache key is the whole request (query, number of hits retrieved, etc.), plus...

FWIW I could confirm a speedup as well with this change on wiibigall.

This suggests that the `fined~2` query doesn't drop exactly the same hits by score, which in-turn means that my suggestion is not correct and isn't actually always the smallest float...

I played a bit more with your change, and it looks like we could make things even further as a follow-up through vectorization by using `(Int|Float)Vector#compress`.

Thinking a bit more about this problem, finding the smallest float that meets the condition may not always be cheap. However, finding a good-enough float should be easy, and it's...