Started by upstream project "Lucene-MMAPv2-Windows" build number 4,0184018Lucene-MMAPv2-Windowsjob/Lucene-MMAPv2-Windows/2116bc9adc96cc58d1e20761d961a2ab865eaede3962bc9adc96cc58d1e20761d961a2ab865eaede3962refs/remotes/origin/mainbc9adc96cc58d1e20761d961a2ab865eaede3962bc9adc96cc58d1e20761d961a2ab865eaede3962refs/remotes/origin/mainbc9adc96cc58d1e20761d961a2ab865eaede3962bc9adc96cc58d1e20761d961a2ab865eaede3962refs/remotes/origin/mainhttps://gitbox.apache.org/repos/asf/lucene.git081018195testReportfalseJava: 64bit/hotspot/jdk-26.0.2 -XX:+UseCompressedOops -XX:+UseG1GC#2116604236569164Lucene-MMAPv2-macOS #21162116falsefalse2116231887SUCCESS1789333514037https://jenkins.thetaphi.de/view/Lucene/job/Lucene-MMAPv2-macOS/2116/macOS VMlucene/core/src/java/org/apache/lucene/search/ByteVectorSimilarityQuery.javalucene/core/src/test/org/apache/lucene/search/TestFloatVectorSimilarityQuery.javalucene/MIGRATE.mdlucene/core/src/test/org/apache/lucene/search/TestVectorSimilarityCollector.javalucene/core/src/test/org/apache/lucene/search/TestByteVectorSimilarityQuery.javalucene/core/src/test/org/apache/lucene/search/TestExplicitByteVectorSimilarityQuery.javalucene/core/src/java/org/apache/lucene/search/ExplicitVectorSimilarityCollector.javalucene/core/src/test/org/apache/lucene/search/TestExplicitFloatVectorSimilarityQuery.javalucene/core/src/java/org/apache/lucene/search/FloatVectorSimilarityQuery.javalucene/CHANGES.txtlucene/core/src/test/org/apache/lucene/search/BaseExplicitVectorSimilarityQueryTestCase.javabc9adc96cc58d1e20761d961a2ab865eaede39621789329999000https://jenkins.thetaphi.de/user/noreplynoreplynoreply@github.comBackwards-compatibility changes for [Byte|Float]VectorSimilarityQuery (#16654) - Lucene 10.5.0 (#15784) switched `[Byte|Float]VectorSimilarityQuery` from explicit to adaptive HNSW graph traversal but kept the constructor signatures unchanged, so the two positional float arguments silently changed meaning from `(traversalSimilarity, resultSimilarity)` to `(resultSimilarity, decay)`. - Make the public constructors `private` to turn the silent behavior change into a compilation error on upgrade to 10.5.2 - Both behaviors are now exposed as nested classes: `[Byte|Float]VectorSimilarityQuery.Explicit` exposes the Lucene 10.4 behavior and is deprecated (will be removed in a future release), and `[Byte|Float]VectorSimilarityQuery.Adaptive` exposes the 10.5 behavior. 2026-09-13 16:06:39 -0400bc9adc96cc58d1e20761d961a2ab865eaede3962Backwards-compatibility changes for [Byte|Float]VectorSimilarityQuery (#16654)editlucene/CHANGES.txteditlucene/core/src/java/org/apache/lucene/search/ByteVectorSimilarityQuery.javaaddlucene/core/src/test/org/apache/lucene/search/TestExplicitByteVectorSimilarityQuery.javaeditlucene/core/src/test/org/apache/lucene/search/TestFloatVectorSimilarityQuery.javaaddlucene/core/src/test/org/apache/lucene/search/BaseExplicitVectorSimilarityQueryTestCase.javaaddlucene/core/src/java/org/apache/lucene/search/ExplicitVectorSimilarityCollector.javaeditlucene/core/src/test/org/apache/lucene/search/TestByteVectorSimilarityQuery.javaeditlucene/core/src/test/org/apache/lucene/search/TestVectorSimilarityCollector.javaeditlucene/MIGRATE.mdaddlucene/core/src/test/org/apache/lucene/search/TestExplicitFloatVectorSimilarityQuery.javaeditlucene/core/src/java/org/apache/lucene/search/FloatVectorSimilarityQuery.javagithttps://jenkins.thetaphi.de/user/noreplynoreply