issues
Thread
Date
Earlier messages
Later messages
Messages by Thread
Re: [PR] Speed up prefix sums when decoding doc IDs. [lucene]
via GitHub
Re: [PR] Speed up prefix sums when decoding doc IDs. [lucene]
via GitHub
Re: [PR] Speed up prefix sums when decoding doc IDs. [lucene]
via GitHub
Re: [PR] Speed up prefix sums when decoding doc IDs. [lucene]
via GitHub
Re: [PR] Speed up prefix sums when decoding doc IDs. [lucene]
via GitHub
Re: [PR] Speed up prefix sums when decoding doc IDs. [lucene]
via GitHub
[PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene]
via GitHub
Re: [PR] Expose FlatVectorsFormat [lucene]
via GitHub
Re: [PR] Expose FlatVectorsFormat [lucene]
via GitHub
Re: [PR] Expose FlatVectorsFormat [lucene]
via GitHub
Re: [PR] Expose FlatVectorsFormat [lucene]
via GitHub
[PR] nocommit: Revert changes to IndexSearcher brought in by GH#13568 [lucene]
via GitHub
Re: [PR] Revert changes to IndexSearcher brought in by GH#13568 [lucene]
via GitHub
Re: [PR] Revert changes to IndexSearcher brought in by GH#13568 [lucene]
via GitHub
Re: [PR] Revert changes to IndexSearcher brought in by GH#13568 [lucene]
via GitHub
Re: [PR] Revert changes to IndexSearcher brought in by GH#13568 [lucene]
via GitHub
Re: [PR] Revert changes to IndexSearcher brought in by GH#13568 [lucene]
via GitHub
Re: [PR] Revert changes to IndexSearcher brought in by GH#13568 [lucene]
via GitHub
Re: [PR] Revert changes to IndexSearcher brought in by GH#13568 [lucene]
via GitHub
Re: [PR] Revert changes to IndexSearcher brought in by GH#13568 [lucene]
via GitHub
[PR] gh-13653: Call finish() from HnswGraphBuilder.build() [lucene]
via GitHub
Re: [PR] gh-13653: Call finish() from HnswGraphBuilder.build() [lucene]
via GitHub
Re: [PR] gh-13653: Call finish() from HnswGraphBuilder.build() [lucene]
via GitHub
Re: [I] What does the Lucene community think about dimensionality reduction for vectors, and should it be something the library does internally (at merge time perhaps)? [lucene]
via GitHub
[PR] Call HnswGraphBuilder.getCompletedGraph() in 94/95 back-compat writers [lucene]
via GitHub
Re: [PR] Call HnswGraphBuilder.getCompletedGraph() in 94/95 back-compat writers [lucene]
via GitHub
[I] TestHnswFloatVectorGraph.testReadWrite fails on branch 9x [lucene]
via GitHub
Re: [I] TestHnswFloatVectorGraph.testReadWrite fails on branch 9x [lucene]
via GitHub
Re: [I] TestHnswFloatVectorGraph.testReadWrite fails on branch 9x [lucene]
via GitHub
Re: [I] TestHnswFloatVectorGraph.testReadWrite fails on branch 9x [lucene]
via GitHub
Re: [PR] Improve BaseRangeFieldQueryTestCase#verify failure output [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. (#13636) [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. (#13636) [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. (#13636) [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. (#13636) [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. (#13636) [lucene]
via GitHub
[PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
Re: [PR] Add a Better Binary Quantizer (RaBitQ) format for dense vectors [lucene]
via GitHub
[I] Add higher quantization level for kNN vector search [lucene]
via GitHub
Re: [I] Add higher quantization level for kNN vector search [lucene]
via GitHub
[PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
Re: [PR] Fix eclipse ide settings generation [lucene]
via GitHub
[PR] gh-13640: Connect hnsw graph components when flushing [lucene]
via GitHub
Re: [PR] gh-13640: Connect hnsw graph components when flushing [lucene]
via GitHub
Re: [PR] gh-13640: Connect hnsw graph components when flushing [lucene]
via GitHub
Re: [PR] Compare the missing value with the top value even after the hit queue is full [lucene]
via GitHub
Re: [PR] Compare the missing value with the top value even after the hit queue is full [lucene]
via GitHub
Re: [PR] Compare the missing value with the top value even after the hit queue is full [lucene]
via GitHub
Re: [PR] Compare the missing value with the top value even after the hit queue is full [lucene]
via GitHub
Re: [PR] Compare the missing value with the top value even after the hit queue is full [lucene]
via GitHub
Re: [PR] Compare the missing value with the top value even after the hit queue is full [lucene]
via GitHub
Re: [I] Compare the missing value with the top value even after the hit queue is full [lucene]
via GitHub
Re: [I] Compare the missing value with the top value even after the hit queue is full [lucene]
via GitHub
Re: [I] Compare the missing value with the top value even after the hit queue is full [lucene]
via GitHub
Re: [I] Compare the missing value with the top value even after the hit queue is full [lucene]
via GitHub
[PR] Avoid rare random test failures in TestLongValueFacetCounts [lucene]
via GitHub
Re: [PR] Avoid rare random test failures in TestLongValueFacetCounts [lucene]
via GitHub
[PR] Backport #13568 [lucene]
via GitHub
Re: [PR] Backport #13568 [lucene]
via GitHub
Re: [PR] Backport #13568 [lucene]
via GitHub
Re: [PR] Backport #13568 [lucene]
via GitHub
Re: [PR] Backport #13568 [lucene]
via GitHub
Re: [PR] Terminate automaton after matched the whole prefix for PrefixQuery. [lucene]
via GitHub
Re: [PR] Terminate automaton after matched the whole prefix for PrefixQuery. [lucene]
via GitHub
Re: [PR] Avoid SegmentTermsEnumFrame reload block. [lucene]
via GitHub
Re: [PR] Avoid SegmentTermsEnumFrame reload block. [lucene]
via GitHub
Re: [I] IndexableField changes its IndexableFieldType when the index is re-opened for reading [LUCENE-7171] [lucene]
via GitHub
Re: [I] IndexableField changes its IndexableFieldType when the index is re-opened for reading [LUCENE-7171] [lucene]
via GitHub
[PR] Two fixes for recently-added HnswGraphBuilder.connectComponents: [lucene]
via GitHub
Re: [PR] Two fixes for recently-added HnswGraphBuilder.connectComponents: [lucene]
via GitHub
Re: [PR] Two fixes for recently-added HnswGraphBuilder.connectComponents: [lucene]
via GitHub
Re: [PR] expand TestSegmentToThreadMapping coverage w.r.t. (excess) documents per slice [lucene]
via GitHub
Re: [I] TermsQuery as MultiTermQuery can dramatically overestimate its cost [lucene]
via GitHub
Re: [I] TermsQuery as MultiTermQuery can dramatically overestimate its cost [lucene]
via GitHub
Re: [I] TermsQuery as MultiTermQuery can dramatically overestimate its cost [lucene]
via GitHub
Re: [I] TermsQuery as MultiTermQuery can dramatically overestimate its cost [lucene]
via GitHub
[PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
Re: [PR] Unify how missing field entries are handle in knn formats [lucene]
via GitHub
[I] testMergeStability failing for Knn formats [lucene]
via GitHub
Re: [I] testMergeStability failing for Knn formats [lucene]
via GitHub
Re: [I] testMergeStability failing for Knn formats [lucene]
via GitHub
Re: [I] testMergeStability failing for Knn formats [lucene]
via GitHub
Re: [I] testMergeStability failing for Knn formats [lucene]
via GitHub
Re: [I] testMergeStability failing for Knn formats [lucene]
via GitHub
Re: [I] testMergeStability failing for Knn formats [lucene]
via GitHub
Re: [I] testMergeStability failing for Knn formats [lucene]
via GitHub
Re: [I] testMergeStability failing for Knn formats [lucene]
via GitHub
Re: [I] Improve AbstractMultiTermQueryConstantScoreWrapper#RewritingWeight ScorerSupplier cost estimation [lucene]
via GitHub
[PR] These attributes are better for the final state(#13628)(#13630) [lucene]
via GitHub
Re: [PR] These attributes are better for the final state(#13628)(#13630) [lucene]
via GitHub
Re: [PR] These attributes are better for the final state(#13628)(#13630) [lucene]
via GitHub
Re: [PR] These attributes are better for the final state(#13628)(#13630) [lucene]
via GitHub
Re: [I] HnwsGraph creates disconnected components [lucene]
via GitHub
Re: [I] HnwsGraph creates disconnected components [lucene]
via GitHub
[I] `gradlew eclipse` no longer works [lucene]
via GitHub
Re: [I] `gradlew eclipse` no longer works [lucene]
via GitHub
Re: [I] `gradlew eclipse` no longer works [lucene]
via GitHub
Re: [I] `gradlew eclipse` no longer works [lucene]
via GitHub
Re: [I] `gradlew eclipse` no longer works [lucene]
via GitHub
Re: [I] `gradlew eclipse` no longer works [lucene]
via GitHub
Re: [I] `gradlew eclipse` no longer works [lucene]
via GitHub
Re: [I] `gradlew eclipse` no longer works [lucene]
via GitHub
Re: [I] `gradlew eclipse` no longer works [lucene]
via GitHub
Re: [I] `gradlew eclipse` no longer works [lucene]
via GitHub
[PR] Knn(Float-->Byte)VectorField javadocs update in KnnByteVectorQuery [lucene]
via GitHub
Re: [PR] Knn(Float-->Byte)VectorField javadocs update in KnnByteVectorQuery [lucene]
via GitHub
[PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Re: [PR] Optimize decoding blocks of postings using the vector API. [lucene]
via GitHub
Earlier messages
Later messages