dnhatn opened a new pull request #389: URL: https://github.com/apache/lucene/pull/389
We introduced invalid accesses for sorted set doc values in [LUCENE-9613](https://issues.apache.org/jira/browse/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 ](https://github.com/apache/lucene/blob/cdfa11b1582ead89547b08c4c41c13712550d4ba/lucene/core/src/java/org/apache/lucene/util/packed/DirectWriter.java#L152-L155)bytes make these invalid accesses perfectly fine. To reproduce this issue, we need to use at least 20 bits per value for the ordinals. The Machine Learning team at Elastic uses a complex doc values setup and [uncovers](https://github.com/elastic/elasticsearch/issues/78785) this bug with a Elasticsearch 8.0 nightly build. Fortunately, this is an unreleased bug in both Lucene and Elasticsearch. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
