[
https://issues.apache.org/jira/browse/LUCENE-9613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17431209#comment-17431209
]
ASF subversion and git services commented on LUCENE-9613:
---------------------------------------------------------
Commit 8b68bf60c9871ecb200f64c64bf55eb6ac456c0e in lucene's branch
refs/heads/hnsw from Nhat Nguyen
[ https://gitbox.apache.org/repos/asf?p=lucene.git;h=8b68bf6 ]
LUCENE-10159: Fix invalid access in sorted set dv (#389)
We introduced invalid accesses for sorted set doc values in LUCENE-9613.
However, the issue has been unnoticed because the ordinals in doc values
tests aren't complex enough to use high packed bits, and the 3 padding
bytes make these invalid accesses perfectly fine. To reproduce this
issue, we need to use at least 20 bits per value for the ordinals.
> Create blocks for ords when it helps in Lucene80DocValuesFormat
> ---------------------------------------------------------------
>
> Key: LUCENE-9613
> URL: https://issues.apache.org/jira/browse/LUCENE-9613
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Adrien Grand
> Priority: Minor
> Fix For: main (9.0)
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Currently for sorted(-set) values, we always write ords using
> log2(valueCount) bits per entry. However in several cases like when the field
> is used in the index sort, or if one value is _very_common, splitting into
> blocks like we do for numerics would help.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
