You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@lucene.apache.org by ja...@apache.org on 2026/02/04 01:52:03 UTC
(lucene) 01/02: Update documentation for Lucene104PostingsFormat (#15625)
This is an automated email from the ASF dual-hosted git repository.
jainankitk pushed a commit to branch branch_10_4
in repository https://gitbox.apache.org/repos/asf/lucene.git
commit b095a8316c502fb45ab7463a92c596f8dd5914f4
Author: 兆森 <wa...@gmail.com>
AuthorDate: Thu Jan 29 07:57:31 2026 +0800
Update documentation for Lucene104PostingsFormat (#15625)
---
lucene/CHANGES.txt | 2 ++
.../org/apache/lucene/codecs/lucene104/Lucene104PostingsFormat.java | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/lucene/CHANGES.txt b/lucene/CHANGES.txt
index 9567cfd39de..cad855d1c07 100644
--- a/lucene/CHANGES.txt
+++ b/lucene/CHANGES.txt
@@ -226,6 +226,8 @@ Other
* GITHUB#15341: Align float vectors on disk to 64 bytes, for optimal performance on Arm Neoverse
machines (including vectors inside CFS files). (Mike McCandless, Kaival Parikh)
+* GITHUB#15619: Update documentation in Lucene104PostingsFormat. with 259 documents, the first 256 document ids should be encoded as one packed block (Lyon-NEU)
+
Build
---------------------
* Upgrade forbiddenapis to version 3.10. (Uwe Schindler)
diff --git a/lucene/core/src/java/org/apache/lucene/codecs/lucene104/Lucene104PostingsFormat.java b/lucene/core/src/java/org/apache/lucene/codecs/lucene104/Lucene104PostingsFormat.java
index 7f901bd90dc..7517a3509c7 100644
--- a/lucene/core/src/java/org/apache/lucene/codecs/lucene104/Lucene104PostingsFormat.java
+++ b/lucene/core/src/java/org/apache/lucene/codecs/lucene104/Lucene104PostingsFormat.java
@@ -51,7 +51,7 @@ import org.apache.lucene.util.packed.PackedInts;
* <p>When the postings are long enough, Lucene104PostingsFormat will try to encode most
* integer data as a packed block.
* <p>Take a term with 259 documents as an example, the first 256 document ids are encoded as
- * two packed blocks, while the remaining 3 are encoded as one VInt block.
+ * one packed block, while the remaining 3 are encoded as one VInt block.
* <p>Different kinds of data are always encoded separately into different packed blocks, but
* may possibly be interleaved into the same VInt block.
* <p>This strategy is applied to pairs: <document number, frequency>, <position,