issues  

Messages by Thread

• • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
  • Re: [PR] Enable Block-Max WAND dynamic pruning for FunctionScoreQuery via DocValuesSkipper (+422% QPS) [lucene] via GitHub
• [PR] deps(java): bump org.apache.opennlp:opennlp-tools from 2.5.10 to 2.5.11 [lucene] via GitHub
  • Re: [PR] deps(java): bump org.apache.opennlp:opennlp-tools from 2.5.10 to 2.5.11 [lucene] via GitHub
• [I] [ENH] Block-Max WAND Dynamic Pruning for FunctionScore & Script Queries (+450% QPS / 5.5x Speedup) [lucene] via GitHub
  • Re: [I] [ENH] Block-Max WAND Dynamic Pruning for FunctionScore & Script Queries (+450% QPS / 5.5x Speedup) [lucene] via GitHub
  • Re: [I] [ENH] Block-Max WAND Dynamic Pruning for FunctionScore & Script Queries (+450% QPS / 5.5x Speedup) [lucene] via GitHub
  • Re: [I] [ENH] Block-Max WAND Dynamic Pruning for FunctionScore & Script Queries (+450% QPS / 5.5x Speedup) [lucene] via GitHub
• [PR] GlobalOrdinalsWithScoreCollector to accumulate scores in double precision [lucene] via GitHub
  • Re: [PR] GlobalOrdinalsWithScoreCollector to accumulate scores in double precision [lucene] via GitHub
  • Re: [PR] GlobalOrdinalsWithScoreCollector to accumulate scores in double precision [lucene] via GitHub
• [I] Separate sequential-read from merge in StoredFieldsReader (allow different instances for read vs merge [lucene] via GitHub
• [I] [ENH]: Adaptive Facet Engine: Single-Pass Posting-Based Aggregation for Low-Cardinality Fields (+465% QPS) [lucene] via GitHub
  • Re: [I] [ENH]: Adaptive Facet Engine: Single-Pass Posting-Based Aggregation for Low-Cardinality Fields (+465% QPS) [lucene] via GitHub
  • Re: [I] [ENH]: Adaptive Facet Engine: Single-Pass Posting-Based Aggregation for Low-Cardinality Fields (+465% QPS) [lucene] via GitHub
• [I] Incorporate DocValuesSkipper into IndexOrDocValuesQuery's cost decision [lucene] via GitHub
  • Re: [I] Incorporate DocValuesSkipper into IndexOrDocValuesQuery's cost decision [lucene] via GitHub
• [PR] Smarter use of sort-field optimizations in DV range queries [lucene] via GitHub
  • Re: [PR] Smarter use of sort-field optimizations in DV range queries [lucene] via GitHub
  • Re: [PR] Smarter use of sort-field optimizations in DV range queries [lucene] via GitHub
  • Re: [PR] Smarter use of sort-field optimizations in DV range queries [lucene] via GitHub
  • Re: [PR] Smarter use of sort-field optimizations in DV range queries [lucene] via GitHub
• [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
  • Re: [PR] Add (configurable) guards for complexity of expressions [lucene] via GitHub
• [PR] Convert Hunspell Dictionary affix directive parsing else-if chain to … [lucene] via GitHub
  • Re: [PR] Convert Hunspell Dictionary affix directive parsing else-if chain to … [lucene] via GitHub
• [I] ENH: Convert Hunspell Dictionary affix directive parsing else-if chain to switch [lucene] via GitHub
• [I] branch_10x: KnnVectorsReader.finishMerge() has no caller — merges permanently flip shared vector inputs to SEQUENTIAL read-advice [lucene] via GitHub
  • Re: [I] branch_10x: KnnVectorsReader.finishMerge() has no caller — merges permanently flip shared vector inputs to SEQUENTIAL read-advice [lucene] via GitHub
  • Re: [I] branch_10x: KnnVectorsReader.finishMerge() has no caller — merges permanently flip shared vector inputs to SEQUENTIAL read-advice [lucene] via GitHub
  • Re: [I] branch_10x: KnnVectorsReader.finishMerge() has no caller — merges permanently flip shared vector inputs to SEQUENTIAL read-advice [lucene] via GitHub
• [I] HNSW-wrapped scalar-quantized fields never hit the centroid fast-path: every delete-free merge re-reads all source floats to recompute a value it already stores [lucene] via GitHub
  • Re: [I] HNSW-wrapped scalar-quantized fields never hit the centroid fast-path: every delete-free merge re-reads all source floats to recompute a value it already stores [lucene] via GitHub
  • Re: [I] HNSW-wrapped scalar-quantized fields never hit the centroid fast-path: every delete-free merge re-reads all source floats to recompute a value it already stores [lucene] via GitHub
  • Re: [I] HNSW-wrapped scalar-quantized fields never hit the centroid fast-path: every delete-free merge re-reads all source floats to recompute a value it already stores [lucene] via GitHub
  • Re: [I] HNSW-wrapped scalar-quantized fields never hit the centroid fast-path: every delete-free merge re-reads all source floats to recompute a value it already stores [lucene] via GitHub
• [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
  • Re: [PR] Incremental doc-values updates [lucene] via GitHub
• [PR] Support intra-segment search in the query profiler with per-slice and per-partition breakdowns [lucene] via GitHub
  • Re: [PR] Support intra-segment search in the query profiler with per-slice and per-partition breakdowns [lucene] via GitHub
• [PR] Use ArrayDeque for JapaneseCompletionFilter output buffering [lucene] via GitHub
  • Re: [PR] Use ArrayDeque for JapaneseCompletionFilter output buffering [lucene] via GitHub
• [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
  • Re: [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
  • Re: [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
  • Re: [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
  • Re: [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
  • Re: [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
  • Re: [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
  • Re: [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
  • Re: [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
  • Re: [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
  • Re: [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
  • Re: [PR] Wrap dropped-FP scalar-quantized float values so scoring stays quantized [lucene] via GitHub
• [PR] perf: optimize StateSet.equals to eliminate heap allocations during a… [lucene] via GitHub
  • Re: [PR] perf: optimize StateSet.equals to eliminate heap allocations during a… [lucene] via GitHub
  • Re: [PR] perf: optimize StateSet.equals to eliminate heap allocations during a… [lucene] via GitHub
• [I] ENH: Optimize StateSet.equals to avoid array allocation and sorting in Operations.determinize() [lucene] via GitHub
• [PR] deps(java): bump junit5 from 6.1.1 to 6.1.2 [lucene] via GitHub
  • Re: [PR] deps(java): bump junit5 from 6.1.1 to 6.1.2 [lucene] via GitHub
• Re: [I] Improve comparator when search sort field does not exist [lucene] via GitHub
• [PR] GITHUB#12370: early-terminate string sort when field is missing from the whole index [lucene] via GitHub
  • Re: [PR] GITHUB#12370: early-terminate string sort when field is missing from the whole index [lucene] via GitHub
  • Re: [PR] GITHUB#12370: early-terminate string sort when field is missing from the whole index [lucene] via GitHub
  • Re: [PR] GITHUB#12370: early-terminate string sort when field is missing from the whole index [lucene] via GitHub
  • Re: [PR] GITHUB#12370: early-terminate string sort when field is missing from the whole index [lucene] via GitHub
  • Re: [PR] GITHUB#12370: early-terminate string sort when field is missing from the whole index [lucene] via GitHub
  • Re: [PR] GITHUB#12370: early-terminate string sort when field is missing from the whole index [lucene] via GitHub
• [PR] Correct Bayesian score fusion semantics and pruning [lucene] via GitHub
  • Re: [PR] Correct Bayesian score fusion semantics and pruning [lucene] via GitHub
  • Re: [PR] Correct Bayesian score fusion semantics and pruning [lucene] via GitHub
• [PR] Do not drop strictly competitive boundary candidates in filtered HNSW search [lucene] via GitHub
  • Re: [PR] Do not drop strictly competitive boundary candidates in filtered HNSW search [lucene] via GitHub
  • Re: [PR] Do not drop strictly competitive boundary candidates in filtered HNSW search [lucene] via GitHub
• [I] TestJoinUtil.testRandomOrdinalsJoin fails due to float precision in GlobalOrdinalsWithScoreCollector [lucene] via GitHub
  • Re: [I] TestJoinUtil.testRandomOrdinalsJoin fails due to float precision in GlobalOrdinalsWithScoreCollector [lucene] via GitHub
  • Re: [I] TestJoinUtil.testRandomOrdinalsJoin fails due to float precision in GlobalOrdinalsWithScoreCollector [lucene] via GitHub
• [PR] Binary search unequal-length suffixes in leaf term blocks. [lucene] via GitHub
  • Re: [PR] Binary search unequal-length suffixes in leaf term blocks. [lucene] via GitHub
  • Re: [PR] Binary search unequal-length suffixes in leaf term blocks. [lucene] via GitHub
  • Re: [PR] Binary search unequal-length suffixes in leaf term blocks. [lucene] via GitHub
  • Re: [PR] Binary search unequal-length suffixes in leaf term blocks. [lucene] via GitHub
• [PR] Fix PointInSetQuery#ramBytesUsed to include retained bounds arrays [lucene] via GitHub
  • Re: [PR] Fix PointInSetQuery#ramBytesUsed to include retained bounds arrays [lucene] via GitHub
  • Re: [PR] Fix PointInSetQuery#ramBytesUsed to include retained bounds arrays [lucene] via GitHub
  • Re: [PR] Fix PointInSetQuery#ramBytesUsed to include retained bounds arrays [lucene] via GitHub
• [I] PointInSetQuery#ramBytesUsed under-reports memory: retained lowerPoint / upperPoint arrays not accounted for [lucene] via GitHub
• [PR] Fix MultiLeafKnnCollector global heap update bug [lucene] via GitHub
  • Re: [PR] Fix MultiLeafKnnCollector global heap update bug [lucene] via GitHub
• Re: [I] TopFieldCollector mistakenly assumes that all leaves share the same index sort [lucene] via GitHub
  • Re: [I] TopFieldCollector mistakenly assumes that all leaves share the same index sort [lucene] via GitHub
• [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
  • Re: [PR] Restore HNSW graph reuse during merges under per-field vectors formats [lucene] via GitHub
• Re: [I] PathHierarchyTokenizer "ancestor search" use case broken in lucene >= 10.0 [lucene] via GitHub
• [PR] GITHUB#15769: Restore PathHierarchyTokenizer synonym positions for ancestor-path search [lucene] via GitHub
  • Re: [PR] GITHUB#15769: Restore PathHierarchyTokenizer synonym positions for ancestor-path search [lucene] via GitHub
  • Re: [PR] GITHUB#15769: Restore PathHierarchyTokenizer synonym positions for ancestor-path search [lucene] via GitHub
• [PR] Speed up TestHnswMergeAbort and make its assertion deterministic [lucene] via GitHub
  • Re: [PR] Speed up TestHnswMergeAbort and make its assertion deterministic [lucene] via GitHub
  • Re: [PR] Speed up TestHnswMergeAbort and make its assertion deterministic [lucene] via GitHub
  • Re: [PR] Speed up TestHnswMergeAbort and make its assertion deterministic [lucene] via GitHub
  • Re: [PR] Speed up TestHnswMergeAbort and make its assertion deterministic [lucene] via GitHub
  • Re: [PR] Speed up TestHnswMergeAbort and make its assertion deterministic [lucene] via GitHub
  • Re: [PR] Speed up TestHnswMergeAbort and make its assertion deterministic [lucene] via GitHub
• [I] HNSW graph reuse during merge is silently disabled under per-field codecs since 10.4.0 [lucene] via GitHub
  • Re: [I] HNSW graph reuse during merge is silently disabled under per-field codecs since 10.4.0 [lucene] via GitHub
  • Re: [I] HNSW graph reuse during merge is silently disabled under per-field codecs since 10.4.0 [lucene] via GitHub
• [PR] Avoid redundant addresses.get() in sorted numeric rangeIntoBitSet [lucene] via GitHub
  • Re: [PR] Avoid redundant addresses.get() in sorted numeric rangeIntoBitSet [lucene] via GitHub
  • Re: [PR] Avoid redundant addresses.get() in sorted numeric rangeIntoBitSet [lucene] via GitHub
• [I] PR benchmark bot for Lucene? [lucene] via GitHub
  • Re: [I] PR benchmark bot for Lucene? [lucene] via GitHub
• [I] Test suite `TestHnswMergeAbort` slows down build [lucene] via GitHub
  • Re: [I] Test suite `TestHnswMergeAbort` slows down build [lucene] via GitHub
  • Re: [I] Test suite `TestHnswMergeAbort` slows down build [lucene] via GitHub
  • Re: [I] Test suite `TestHnswMergeAbort` slows down build [lucene] via GitHub
  • Re: [I] Test suite `TestHnswMergeAbort` slows down build [lucene] via GitHub
• [PR] Handle inconsistent schema on flush with index sorts (#15125) [lucene] via GitHub
  • Re: [PR] Handle inconsistent schema on flush with index sorts (#15125) [lucene] via GitHub
  • [PR] Handle inconsistent schema on flush with index sorts (#15125) [lucene] via GitHub
  • Re: [PR] Handle inconsistent schema on flush with index sorts (#15125) [lucene] via GitHub
• [PR] Bulk nextDocsAndScores for constant-score disjunction clauses [lucene] via GitHub
  • Re: [PR] Bulk nextDocsAndScores for constant-score disjunction clauses [lucene] via GitHub
  • Re: [PR] Bulk nextDocsAndScores for constant-score disjunction clauses [lucene] via GitHub
  • Re: [PR] Bulk nextDocsAndScores for constant-score disjunction clauses [lucene] via GitHub
  • Re: [PR] Bulk nextDocsAndScores for constant-score disjunction clauses [lucene] via GitHub
  • Re: [PR] Bulk nextDocsAndScores for constant-score disjunction clauses [lucene] via GitHub
  • Re: [PR] Bulk nextDocsAndScores for constant-score disjunction clauses [lucene] via GitHub
  • Re: [PR] Bulk nextDocsAndScores for constant-score disjunction clauses [lucene] via GitHub
  • Re: [PR] Bulk nextDocsAndScores for constant-score disjunction clauses [lucene] via GitHub

• Earlier messages
• Later messages