issues
Thread
Date
Earlier messages
Messages by Thread
[PR] Reduce the overhead of `IndexInput#prefetch` when data is cached in RAM. [lucene]
via GitHub
Re: [PR] Reduce the overhead of `IndexInput#prefetch` when data is cached in RAM. [lucene]
via GitHub
Re: [PR] Reduce the overhead of `IndexInput#prefetch` when data is cached in RAM. [lucene]
via GitHub
Re: [PR] Reduce the overhead of `IndexInput#prefetch` when data is cached in RAM. [lucene]
via GitHub
Re: [PR] Reduce the overhead of `IndexInput#prefetch` when data is cached in RAM. [lucene]
via GitHub
Re: [PR] Reduce the overhead of `IndexInput#prefetch` when data is cached in RAM. [lucene]
via GitHub
Re: [PR] Reduce the overhead of `IndexInput#prefetch` when data is cached in RAM. [lucene]
via GitHub
Re: [PR] Reduce the overhead of `IndexInput#prefetch` when data is cached in RAM. [lucene]
via GitHub
Re: [PR] Speedup concurrent multi-segment HNSW graph search 2 [lucene]
via GitHub
[I] Reproducible failure TestHnswByteVectorGraph.testSortedAndUnsortedIndicesReturnSameResults [lucene]
via GitHub
Re: [I] Reproducible failure TestHnswByteVectorGraph.testSortedAndUnsortedIndicesReturnSameResults [lucene]
via GitHub
Re: [I] Reproducible failure TestHnswByteVectorGraph.testSortedAndUnsortedIndicesReturnSameResults [lucene]
via GitHub
[PR] lucene-monitor: make TermFilteredPresearcher.ANYTOKEN[_FIELD] public [lucene]
via GitHub
Re: [PR] lucene-monitor: make TermFilteredPresearcher.ANYTOKEN[_FIELD] public [lucene]
via GitHub
Re: [I] Improve LongRange execution for ranges that have min value as Long.MIN_VALUE and max value as Long.MAX_VALUE or min as 0, and max as 2^64-1 [lucene]
via GitHub
Re: [I] Improve LongRange execution for ranges that have min value as Long.MIN_VALUE and max value as Long.MAX_VALUE or min as 0, and max as 2^64-1 [lucene]
via GitHub
Re: [I] Improve LongRange execution for ranges that have min value as Long.MIN_VALUE and max value as Long.MAX_VALUE or min as 0, and max as 2^64-1 [lucene]
via GitHub
[PR] Fix points writing with no values [lucene]
via GitHub
Re: [PR] Fix points writing with no values [lucene]
via GitHub
Re: [PR] Fix points writing with no values [lucene]
via GitHub
[I] Reproducible failure TestIndexWriterExceptions2.testBasics [lucene]
via GitHub
Re: [I] Reproducible failure TestIndexWriterExceptions2.testBasics [lucene]
via GitHub
Re: [I] Reproducible failure TestIndexWriterExceptions2.testBasics [lucene]
via GitHub
[PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
Re: [PR] Fix IntegerOverflow exception in postings encoding as group-varint [lucene]
via GitHub
[PR] Fix bug in SQ when just a single vector present [lucene]
via GitHub
Re: [PR] Fix bug in SQ when just a single vector present in a segment [lucene]
via GitHub
[I] DataOutput.writeGroupVInts throws IntegerOverflow exception during merging [lucene]
via GitHub
Re: [I] DataOutput.writeGroupVInts throws IntegerOverflow exception during merging [lucene]
via GitHub
Re: [I] DataOutput.writeGroupVInts throws IntegerOverflow exception during merging [lucene]
via GitHub
Re: [I] DataOutput.writeGroupVInts throws IntegerOverflow exception during merging [lucene]
via GitHub
Re: [I] DataOutput.writeGroupVInts throws IntegerOverflow exception during merging [lucene]
via GitHub
Re: [I] DataOutput.writeGroupVInts throws IntegerOverflow exception during merging [lucene]
via GitHub
Re: [I] DataOutput.writeGroupVInts throws IntegerOverflow exception during merging [lucene]
via GitHub
[I] Reproducible failure TestOrdinalMap.testRamBytesUsed [lucene]
via GitHub
[I] Reproducible failure org.apache.lucene.search.TestBlockMaxConjunction [lucene]
via GitHub
[PR] Add a double addressing vector scorer [lucene]
via GitHub
Re: [PR] Add a double addressing vector scorer [lucene]
via GitHub
Re: [PR] Add a double addressing vector scorer [lucene]
via GitHub
Re: [PR] Add a double addressing vector scorer [lucene]
via GitHub
Re: [PR] Add a double addressing vector scorer [lucene]
via GitHub
Re: [PR] Add a double addressing vector scorer [lucene]
via GitHub
Re: [PR] Add a double addressing vector scorer [lucene]
via GitHub
Re: [PR] Add a double addressing vector scorer [lucene]
via GitHub
[PR] Fix weird NRT bug #13353 [lucene]
via GitHub
Re: [PR] Fix weird NRT bug #13353 [lucene]
via GitHub
Re: [PR] Fix weird NRT bug #13353 [lucene]
via GitHub
Re: [I] Remove Accountable interface where it's not needed [lucene]
via GitHub
Re: [I] Remove Accountable interface where it's not needed [lucene]
via GitHub
[PR] Replace Map<Integer, Object> by primitive IntObjectHashMap. [lucene]
via GitHub
Re: [PR] Replace Map<Integer, Object> by primitive IntObjectHashMap. [lucene]
via GitHub
Re: [PR] Replace Map<Integer, Object> by primitive IntObjectHashMap. [lucene]
via GitHub
[PR] Add per-field knn vector format info in SegmentInfo [lucene]
via GitHub
Re: [PR] Add per-field knn vector format info in SegmentInfo [lucene]
via GitHub
Re: [PR] Add per-field knn vector format info in SegmentInfo [lucene]
via GitHub
Re: [PR] Add per-field knn vector format info in SegmentInfo [lucene]
via GitHub
Re: [PR] Protect against nan & inf values in quantizer and test with tiny vectors [lucene]
via GitHub
Re: [PR] Backport to 9x: Reduce duplication in taxonomy facets; always do counts #12966 [lucene]
via GitHub
Re: [PR] Backport to 9x: Reduce duplication in taxonomy facets; always do counts #12966 [lucene]
via GitHub
Re: [PR] Make `IndexInput#prefetch` take an offset. [lucene]
via GitHub
Re: [PR] Make `IndexInput#prefetch` take an offset. [lucene]
via GitHub
Re: [PR] Make `IndexInput#prefetch` take an offset. [lucene]
via GitHub
Re: [PR] Ensure negative scores aren not returned from scalar quantization scorer [lucene]
via GitHub
Re: [PR] Ensure negative scores aren not returned from scalar quantization scorer [lucene]
via GitHub
[PR] Fix vector scorer interface consistency [lucene]
via GitHub
Re: [PR] Fix vector scorer interface consistency [lucene]
via GitHub
Re: [PR] Fix vector scorer interface consistency [lucene]
via GitHub
Re: [PR] Fix vector scorer interface consistency [lucene]
via GitHub
Re: [PR] Fix vector scorer interface consistency [lucene]
via GitHub
Re: [PR] Fix vector scorer interface consistency [lucene]
via GitHub
[PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Prefetch postings data. [lucene]
via GitHub
Re: [PR] Use IndexInput#prefetch for postings, skip data and impacts [lucene]
via GitHub
[PR] Always add sub query explanations to DisjunctionMaxQuery [lucene]
via GitHub
Re: [PR] Add sub query explanations in DisjunctionMaxQuery#explain on no-match [lucene]
via GitHub
Re: [PR] Add sub query explanations in DisjunctionMaxQuery#explain on no-match [lucene]
via GitHub
Re: [PR] Add sub query explanations in DisjunctionMaxQuery#explain on no-match [lucene]
via GitHub
Re: [PR] Add sub query explanations in DisjunctionMaxQuery#explain on no-match [lucene]
via GitHub
[PR] Fix TestHnswByteVectorGraph.testSortedAndUnsortedIndicesReturnSameResults [lucene]
via GitHub
Re: [PR] Fix TestHnswByteVectorGraph.testSortedAndUnsortedIndicesReturnSameResults [lucene]
via GitHub
Re: [PR] Fix TestHnswByteVectorGraph.testSortedAndUnsortedIndicesReturnSameResults [lucene]
via GitHub
Re: [PR] Fix TestHnswByteVectorGraph.testSortedAndUnsortedIndicesReturnSameResults [lucene]
via GitHub
Re: [PR] Fix TestHnswByteVectorGraph.testSortedAndUnsortedIndicesReturnSameResults [lucene]
via GitHub
Re: [PR] Fix TestHnswByteVectorGraph.testSortedAndUnsortedIndicesReturnSameResults [lucene]
via GitHub
Re: [PR] Fix TestHnswByteVectorGraph.testSortedAndUnsortedIndicesReturnSameResults [lucene]
via GitHub
Re: [PR] Fix TestHnswByteVectorGraph.testSortedAndUnsortedIndicesReturnSameResults [lucene]
via GitHub
[PR] Call ArrayUtil.copyOf instead of ArrayUtil.copySubArray for full array copy. [lucene]
via GitHub
Re: [PR] Call ArrayUtil.copyArray instead of ArrayUtil.copySubArray for full array copy. [lucene]
via GitHub
Re: [PR] Use `IndexInput#prefetch` for terms dictionary lookups. [lucene]
via GitHub
Re: [PR] Use `IndexInput#prefetch` for terms dictionary lookups. [lucene]
via GitHub
Re: [PR] Use `IndexInput#prefetch` for terms dictionary lookups. [lucene]
via GitHub
Re: [PR] Use `IndexInput#prefetch` for terms dictionary lookups. [lucene]
via GitHub
Re: [PR] Use `IndexInput#prefetch` for terms dictionary lookups. [lucene]
via GitHub
Re: [PR] Early terminate visit BKD leaf when current value greater than upper point in sorted dim. [lucene]
via GitHub
Re: [PR] Backport to 9x: Reduce duplication in taxonomy facets; always do counts #12966x [lucene]
via GitHub
[I] Enhance DisjunctionMaxQuery explanation to include details in case there was no match [lucene]
via GitHub
Re: [I] Enhance DisjunctionMaxQuery explanation to include details in case there was no match [lucene]
via GitHub
[PR] Fix default flat vector scorer supplier sharing backing array [lucene]
via GitHub
Re: [PR] Fix default flat vector scorer supplier sharing backing array [lucene]
via GitHub
Re: [PR] Fix default flat vector scorer supplier sharing backing array [lucene]
via GitHub
Re: [PR] Fix default flat vector scorer supplier sharing backing array [lucene]
via GitHub
Re: [PR] Fix default flat vector scorer supplier sharing backing array [lucene]
via GitHub
Re: [PR] Fix default flat vector scorer supplier sharing backing array [lucene]
via GitHub
Re: [PR] Reuse BitSet when there are deleted documents in the index instead of creating new BitSet [lucene]
via GitHub
Re: [PR] Reuse BitSet when there are deleted documents in the index instead of creating new BitSet [lucene]
via GitHub
[I] Merges sometimes do lots of work even after being aborted [lucene]
via GitHub
[I] NRT failure due to SegmentInfo & File mismatch [lucene]
via GitHub
Re: [I] NRT failure due to FieldInfo & File mismatch [lucene]
via GitHub
Re: [I] NRT failure due to FieldInfo & File mismatch [lucene]
via GitHub
Re: [I] NRT failure due to FieldInfo & File mismatch [lucene]
via GitHub
[I] TestIndexWriterMergePolicy.testStressUpdateSameDocumentWithMergeOnGetReader failure due to DWPT race condition [lucene]
via GitHub
[PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Enable Panama Vector similarities implementation always in the CI [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
Re: [PR] Add a separate option to allow running Panama Vectorization for all tests with suitable C2 defaults [lucene]
via GitHub
[PR] [GENE-2434] - Load vault token from file [lucene-solr]
via GitHub
Re: [PR] [GENE-2434] - Load vault token from file [lucene-solr]
via GitHub
[I] Significant drop in recall for int8 scalar quantization using maximum_inner_product [lucene]
via GitHub
Re: [I] Significant drop in recall for int8 scalar quantization using maximum_inner_product [lucene]
via GitHub
Re: [I] Significant drop in recall for int8 scalar quantization using maximum_inner_product [lucene]
via GitHub
Re: [I] Significant drop in recall for int8 scalar quantization using maximum_inner_product [lucene]
via GitHub
Re: [I] Significant drop in recall for int8 scalar quantization using maximum_inner_product [lucene]
via GitHub
Re: [I] Significant drop in recall for int8 scalar quantization using maximum_inner_product [lucene]
via GitHub
Re: [I] Significant drop in recall for int8 scalar quantization using maximum_inner_product [lucene]
via GitHub
Re: [I] Significant drop in recall for int8 scalar quantization using maximum_inner_product [lucene]
via GitHub
Re: [I] Significant drop in recall for int8 scalar quantization using maximum_inner_product [lucene]
via GitHub
Re: [I] Significant drop in recall for int8 scalar quantization using maximum_inner_product [lucene]
via GitHub
Re: [I] Significant drop in recall for int8 scalar quantization using maximum_inner_product [lucene]
via GitHub
[I] Make intra tasks in IndexingChain.flush parallel execute. [lucene]
via GitHub
Re: [I] Make intra tasks in IndexingChain.flush parallel execute. [lucene]
via GitHub
Re: [I] Make intra tasks in IndexingChain.flush parallel execute. [lucene]
via GitHub
Re: [I] Make intra tasks in IndexingChain.flush parallel execute. [lucene]
via GitHub
Re: [I] Make intra tasks in IndexingChain.flush parallel execute. [lucene]
via GitHub
Re: [PR] Introduce dynamic segment efSearch to Knn{Byte|Float}VectorQuery [lucene]
via GitHub
Re: [PR] Introduce dynamic segment efSearch to Knn{Byte|Float}VectorQuery [lucene]
via GitHub
Re: [PR] Introduce dynamic segment efSearch to Knn{Byte|Float}VectorQuery [lucene]
via GitHub
Re: [PR] Harden BaseDocValuesFormatTestCase (#13346) [lucene]
via GitHub
Re: [PR] Harden BaseDocValuesFormatTestCase (#13346) [lucene]
via GitHub
[PR] Harden BaseDocValuesFormatTestCase [lucene]
via GitHub
Re: [PR] Harden BaseDocValuesFormatTestCase [lucene]
via GitHub
Re: [PR] Harden BaseDocValuesFormatTestCase [lucene]
via GitHub
Re: [PR] Harden BaseDocValuesFormatTestCase [lucene]
via GitHub
Re: [PR] Harden BaseDocValuesFormatTestCase [lucene]
via GitHub
Re: [I] How to run tests with the Panama Vector implementation [lucene]
via GitHub
Re: [I] How to run tests with the Panama Vector implementation [lucene]
via GitHub
Re: [I] How to run tests with the Panama Vector implementation [lucene]
via GitHub
Re: [I] How to run tests with the Panama Vector implementation [lucene]
via GitHub
Earlier messages