Guo Feng
Guo Feng
https://issues.apache.org/jira/browse/LUCENE-10409 #11445
https://issues.apache.org/jira/browse/LUCENE-10366 #11402 Today, we do not rewrite `#readVInt` and `#readVLong` for `ByteBufferIndexInput`. By default, the logic will call `#readByte` several times, and we need to check whether `ByteBuffer` is valid...
https://issues.apache.org/jira/browse/LUCENE-10376 #11412
see https://issues.apache.org/jira/browse/LUCENE-10334 #11370 Changes: 1. Make ForUtil fit for 64bit. 2. Introduce the new `BlockWriter` and `BlockReader`. 3. Replaces `DirectReader` with `BlockReader` and `DirectReader` with `BlockWriter`.
see: https://issues.apache.org/jira/browse/LUCENE-10334 #11370
See https://issues.apache.org/jira/browse/LUCENE-10333 #11369 PS: I'm pushing these codes to quickly see if this approach makes sense to you, I'll add some more tests if this can pass the the first...
TermInSetQuery will avoid caching queries using too much memory, but there is no such limit in PointInSetQuery and PointInSetQueryWithScore, which may have similar problems. I added the logic to these...
**Description** In https://github.com/apache/lucene/pull/12114, we had great numbers for LSB radix sorter when sorting random docs in `SortingDocsEnum` . But we can not take advantage of the LSB radix sorter in...
### Description Immature idea, for discussion purpose :) Today our range query on numbers have two approaches: BKD or DocValue Skipper. The drawback of BKD: * Allocating too much memory...
### Description When benchmarking recently with some OLAP engines (no indexes, no stored fields, only column data), the results showed that they only occupy 50-70% of the storage of `NumericDocvalues`,...