issues  

Messages by Thread

• • Re: [PR] Skip heavy TreeSet opts for the first group in FirstPassGroupingCollector [lucene] via GitHub
  • Re: [PR] Skip heavy TreeSet opts for the first group in FirstPassGroupingCollector [lucene] via GitHub
• Re: [I] Merges kicked off by IndexWriter.addIndexes(CodecReader[]) fail to set estimated size [lucene] via GitHub
• Re: [PR] [Bug] Fix for stored fields force merge regression [lucene] via GitHub
  • Re: [PR] [Bug] Fix for stored fields force merge regression [lucene] via GitHub
• Re: [PR] Move finishMerge to a finally block so it always runs [lucene] via GitHub
  • Re: [PR] Move finishMerge to a finally block so it always runs [lucene] via GitHub
  • Re: [PR] Move finishMerge to a finally block so it always runs [lucene] via GitHub
  • Re: [PR] Move finishMerge to a finally block so it always runs [lucene] via GitHub
  • Re: [PR] Move finishMerge to a finally block so it always runs [lucene] via GitHub
• Re: [PR] Rewrite SortedNumericDocValuesRangeQuery using DocValuesSkippers [lucene] via GitHub
  • Re: [PR] Rewrite SortedNumericDocValuesRangeQuery using DocValuesSkippers [lucene] via GitHub
  • Re: [PR] Rewrite SortedNumericDocValuesRangeQuery using DocValuesSkippers [lucene] via GitHub
• [PR] Early exit while computing globalMin/Max using skipper [lucene] via GitHub
  • Re: [PR] Early exit while computing globalMin/Max using skipper [lucene] via GitHub
  • Re: [PR] Early exit while computing globalMin/Max using skipper [lucene] via GitHub
• [I] Unsupported queries should throw IllegalArgumentException instead. [lucene] via GitHub
  • Re: [I] Unsupported queries should throw IllegalArgumentException instead. [lucene] via GitHub
  • Re: [I] Unsupported queries should throw IllegalArgumentException instead. [lucene] via GitHub
  • Re: [I] Unsupported queries should throw IllegalArgumentException instead. [lucene] via GitHub
• Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
  • Re: [PR] [Draft] Add BandwidthCappedMergeScheduler for enforcing a global merge bandwidth cap [lucene] via GitHub
• Re: [I] Switch over current scalar quantization formats to use `OptimizedScalarQuantizer` [lucene] via GitHub
  • Re: [I] Switch over current scalar quantization formats to use `OptimizedScalarQuantizer` [lucene] via GitHub
  • Re: [I] Switch over current scalar quantization formats to use `OptimizedScalarQuantizer` [lucene] via GitHub
  • Re: [I] Switch over current scalar quantization formats to use `OptimizedScalarQuantizer` [lucene] via GitHub
  • Re: [I] Switch over current scalar quantization formats to use `OptimizedScalarQuantizer` [lucene] via GitHub
  • Re: [I] Switch over current scalar quantization formats to use `OptimizedScalarQuantizer` [lucene] via GitHub
  • Re: [I] Switch over current scalar quantization formats to use `OptimizedScalarQuantizer` [lucene] via GitHub
  • Re: [I] Switch over current scalar quantization formats to use `OptimizedScalarQuantizer` [lucene] via GitHub
  • Re: [I] Switch over current scalar quantization formats to use `OptimizedScalarQuantizer` [lucene] via GitHub
  • Re: [I] Switch over current scalar quantization formats to use `OptimizedScalarQuantizer` [lucene] via GitHub
  • Re: [I] Switch over current scalar quantization formats to use `OptimizedScalarQuantizer` [lucene] via GitHub
• Re: [I] Understand 2025/08/06 nightly benchy regression in KNN indexing [lucene] via GitHub
  • Re: [I] Understand 2025/08/06 nightly benchy regression in KNN indexing [lucene] via GitHub
  • Re: [I] Understand 2025/08/06 nightly benchy regression in KNN indexing [lucene] via GitHub
  • Re: [I] Understand 2025/08/06 nightly benchy regression in KNN indexing [lucene] via GitHub
  • Re: [I] Understand 2025/08/06 nightly benchy regression in KNN indexing [lucene] via GitHub
• Re: [PR] Tessellator should fail if it cannot process a hole [lucene] via GitHub
• Re: [I] RefCountedShatredArena is causing infinite (spin-)loop on close of IndexInput/IndexReader/... due to exception handling [lucene] via GitHub
• [PR] Handle inconsistent schema on flush with index sorts [lucene] via GitHub
  • Re: [PR] Handle inconsistent schema on flush with index sorts [lucene] via GitHub
  • Re: [PR] Handle inconsistent schema on flush with index sorts [lucene] via GitHub
  • Re: [PR] Handle inconsistent schema on flush with index sorts [lucene] via GitHub
  • Re: [PR] Handle inconsistent schema on flush with index sorts [lucene] via GitHub
  • Re: [PR] Handle inconsistent schema on flush with index sorts [lucene] via GitHub
  • Re: [PR] Handle inconsistent schema on flush with index sorts [lucene] via GitHub
• [PR] Use RamUsageEstimator to estimate query size instead of defaulting to 1024 bytes for non-accountable queries. [lucene] via GitHub
  • Re: [PR] Use RamUsageEstimator to estimate query size instead of defaulting to 1024 bytes for non-accountable queries. [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
  • Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
• Re: [PR] Use FixedBitSet#cardinality for counting liveDocs in CheckIndex [lucene] via GitHub
  • Re: [PR] Use FixedBitSet#cardinality for counting liveDocs in CheckIndex [lucene] via GitHub
  • Re: [PR] Use FixedBitSet#cardinality for counting liveDocs in CheckIndex [lucene] via GitHub
• Re: [PR] Fix infinite loop when RefCountedSharedArena's underlying Arena#close fails due to concurrent usage of segments [lucene] via GitHub
  • Re: [PR] Fix infinite loop when RefCountedSharedArena's underlying Arena#close fails due to concurrent usage of segments [lucene] via GitHub
  • Re: [PR] Fix infinite loop when RefCountedSharedArena's underlying Arena#close fails due to concurrent usage of segments [lucene] via GitHub
• Re: [I] MMapDirectory sometimes "leaks" 1000s of maps [lucene] via GitHub
  • Re: [I] MMapDirectory sometimes "leaks" 1000s of maps [lucene] via GitHub
  • Re: [I] MMapDirectory sometimes "leaks" 1000s of maps [lucene] via GitHub
• [PR] Reusing count() for minor refactor in SortedNumericDocValuesRangeQuery [lucene] via GitHub
  • Re: [PR] Reusing count() for minor refactor in SortedNumericDocValuesRangeQuery [lucene] via GitHub
  • Re: [PR] Reusing count() for minor refactor in SortedNumericDocValuesRangeQuery [lucene] via GitHub
  • Re: [PR] Reusing count() for minor refactor in SortedNumericDocValuesRangeQuery [lucene] via GitHub
  • Re: [PR] Reusing count() for minor refactor in SortedNumericDocValuesRangeQuery [lucene] via GitHub
  • Re: [PR] Reusing count() for minor refactor in SortedNumericDocValuesRangeQuery [lucene] via GitHub
• Re: [PR] Adding profiling support for concurrent segment search [lucene] via GitHub
  • Re: [PR] Adding profiling support for concurrent segment search [lucene] via GitHub
  • Re: [PR] Adding profiling support for concurrent segment search [lucene] via GitHub
  • Re: [PR] Adding profiling support for concurrent segment search [lucene] via GitHub
  • Re: [PR] Adding profiling support for concurrent segment search [lucene] via GitHub
  • Re: [PR] Adding profiling support for concurrent segment search [lucene] via GitHub
  • Re: [PR] Adding profiling support for concurrent segment search [lucene] via GitHub
• Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
  • Re: [PR] Rewrite of the GroupVInt optimization without lambdas, varhandles and no code in subclasses [lucene] via GitHub
• Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
  • Re: [PR] Avoid reconstructing HNSW graphs during segment merging. [lucene] via GitHub
• Re: [PR] PostingsDecodingUtil: interchange loops to enable better memory access and SIMD vectorisation [lucene] via GitHub
  • Re: [PR] PostingsDecodingUtil: interchange loops to enable better memory access and SIMD vectorisation [lucene] via GitHub
  • Re: [PR] PostingsDecodingUtil: interchange loops to enable better memory access and SIMD vectorisation [lucene] via GitHub
  • Re: [PR] PostingsDecodingUtil: interchange loops to enable better memory access and SIMD vectorisation [lucene] via GitHub
  • Re: [PR] PostingsDecodingUtil: interchange loops to enable better memory access and SIMD vectorisation [lucene] via GitHub
• Re: [PR] Add estimatedByteSizes to merges kicked off by IndexWriter.addIndexes(CodecReader[]) [lucene] via GitHub
  • Re: [PR] Add estimatedByteSizes to merges kicked off by IndexWriter.addIndexes(CodecReader[]) [lucene] via GitHub
  • Re: [PR] Add estimatedByteSizes to merges kicked off by IndexWriter.addIndexes(CodecReader[]) [lucene] via GitHub
  • Re: [PR] Add estimatedByteSizes to merges kicked off by IndexWriter.addIndexes(CodecReader[]) [lucene] via GitHub
  • Re: [PR] Add estimatedByteSizes to merges kicked off by IndexWriter.addIndexes(CodecReader[]) [lucene] via GitHub
  • Re: [PR] Add estimatedByteSizes to merges kicked off by IndexWriter.addIndexes(CodecReader[]) [lucene] via GitHub
  • Re: [PR] Add estimatedByteSizes to merges kicked off by IndexWriter.addIndexes(CodecReader[]) [lucene] via GitHub
  • Re: [PR] Add estimatedByteSizes to merges kicked off by IndexWriter.addIndexes(CodecReader[]) [lucene] via GitHub
  • Re: [PR] Add estimatedByteSizes to merges kicked off by IndexWriter.addIndexes(CodecReader[]) [lucene] via GitHub
• Re: [PR] DataInput: Unroll loop in readVInt and readVLong [lucene] via GitHub
• Re: [PR] Return the max score from `RandomVectorScorer.bulkScore` [lucene] via GitHub
  • Re: [PR] Return the max score from `RandomVectorScorer.bulkScore` [lucene] via GitHub
  • Re: [PR] Return the max score from `RandomVectorScorer.bulkScore` [lucene] via GitHub
  • Re: [PR] Return the max score from `RandomVectorScorer.bulkScore` [lucene] via GitHub
  • Re: [PR] Return the max score from `RandomVectorScorer.bulkScore` [lucene] via GitHub
• Re: [I] Add optimistic knn search to other vector query types [lucene] via GitHub

• Later messages