issues  

Messages by Thread

• • Re: [PR] Speedup PriorityQueue a little [lucene] via GitHub
  • Re: [PR] Speedup PriorityQueue a little [lucene] via GitHub
  • Re: [PR] Speedup PriorityQueue a little [lucene] via GitHub
• [PR] Misc cleanups to TopScoreDocCollector [lucene] via GitHub
  • Re: [PR] Misc cleanups to TopScoreDocCollector [lucene] via GitHub
  • Re: [PR] Misc cleanups to TopScoreDocCollector [lucene] via GitHub
• [PR] wip: add base test + minor tweaks [lucene] via GitHub
  • Re: [PR] FVH BaseFragmentsBuilder does not properly support colored pre/post tags [lucene] via GitHub
• [I] FVH BaseFragmentsBuilder does not properly support colored pre/post tags [lucene] via GitHub
• [PR] Simplify PForUtil construction and cleanup its code gen a little [lucene] via GitHub
  • Re: [PR] Simplify PForUtil construction and cleanup its code gen a little [lucene] via GitHub
  • Re: [PR] Simplify PForUtil construction and cleanup its code gen a little [lucene] via GitHub
  • Re: [PR] Simplify PForUtil construction and cleanup its code gen a little [lucene] via GitHub
  • Re: [PR] Simplify PForUtil construction and cleanup its code gen a little [lucene] via GitHub
• Re: [PR] Convert BooleanClause class to record class [lucene] via GitHub
  • Re: [PR] Convert BooleanClause class to record class [lucene] via GitHub
• [PR] Move BooleanScorer to work on top of Scorers rather than BulkScorers. [lucene] via GitHub
  • Re: [PR] Move BooleanScorer to work on top of Scorers rather than BulkScorers. [lucene] via GitHub
  • Re: [PR] Move BooleanScorer to work on top of Scorers rather than BulkScorers. [lucene] via GitHub
  • Re: [PR] Move BooleanScorer to work on top of Scorers rather than BulkScorers. [lucene] via GitHub
  • Re: [PR] Make BooleanScorer work on top of Scorers rather than BulkScorers. [lucene] via GitHub
• [PR] Use growNoCopy when copying bytes in BytesRefBuilder [lucene] via GitHub
  • Re: [PR] Use growNoCopy when copying bytes in BytesRefBuilder [lucene] via GitHub
• Re: [I] Should we avoid allocating a byte[] upfront for binary doc values [lucene] via GitHub
  • Re: [I] Should we avoid allocating a byte[] upfront for binary doc values [lucene] via GitHub
  • Re: [I] Should we avoid allocating a byte[] upfront for binary doc values [lucene] via GitHub
• Re: [PR] Avoid reload block when seeking backward in SegmentTermsEnum. [lucene] via GitHub
  • Re: [PR] Avoid reload block when seeking backward in SegmentTermsEnum. [lucene] via GitHub
  • Re: [PR] Avoid reload block when seeking backward in SegmentTermsEnum. [lucene] via GitHub
  • Re: [PR] Avoid reload block when seeking backward in SegmentTermsEnum. [lucene] via GitHub
• [PR] Change StringHelper from abstract to final. [lucene] via GitHub
  • Re: [PR] Change StringHelper from abstract to final. [lucene] via GitHub
  • Re: [PR] Change StringHelper from abstract to final. [lucene] via GitHub
  • Re: [PR] Change StringHelper from abstract to final. [lucene] via GitHub
  • Re: [PR] Change StringHelper from abstract to final. [lucene] via GitHub
  • Re: [PR] Change StringHelper from abstract to final. [lucene] via GitHub
  • Re: [PR] Change StringHelper from abstract to final. [lucene] via GitHub
  • Re: [PR] Change StringHelper from abstract to final. [lucene] via GitHub
  • Re: [PR] Change StringHelper from abstract to final. [lucene] via GitHub
• [PR] Fix StoredFieldsConsumer finish [lucene] via GitHub
  • Re: [PR] Fix StoredFieldsConsumer finish [lucene] via GitHub
  • Re: [PR] Fix StoredFieldsConsumer finish [lucene] via GitHub
  • Re: [PR] Fix StoredFieldsConsumer finish [lucene] via GitHub
  • Re: [PR] Fix StoredFieldsConsumer finish [lucene] via GitHub
• Re: [I] Added capability to auto force merge as much as possible to reduce the number of segments [lucene] via GitHub
• Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
  • Re: [PR] Include java21 source folders to gradle source sets [lucene] via GitHub
• [PR] Use Arrays.mismatch in FSTCompiler#add. [lucene] via GitHub
  • Re: [PR] Use Arrays.mismatch in FSTCompiler#add. [lucene] via GitHub
  • Re: [PR] Use Arrays.mismatch in FSTCompiler#add. [lucene] via GitHub
  • Re: [PR] Use Arrays.mismatch in FSTCompiler#add. [lucene] via GitHub
  • Re: [PR] Use Arrays.mismatch in FSTCompiler#add. [lucene] via GitHub
  • Re: [PR] Use Arrays.mismatch in FSTCompiler#add. [lucene] via GitHub
  • Re: [PR] Use Arrays.mismatch in FSTCompiler#add. [lucene] via GitHub
• [PR] Remove TODO in FSTCompiler#freezeTail. [lucene] via GitHub
  • Re: [PR] Remove TODO in FSTCompiler#freezeTail. [lucene] via GitHub
• Re: [I] Find more classes in main branch that can be converted to record classes [lucene] via GitHub
  • Re: [I] Find more classes in main branch that can be converted to record classes [lucene] via GitHub
• Re: [I] Improve Lucene's I/O concurrency [lucene] via GitHub
• [I] Can we use Panama Vector API for quantizing vectors? [lucene] via GitHub
• [I] How to use hnsw int4 when loading index [lucene] via GitHub
  • Re: [I] How to use hnsw int4 when loading index [lucene] via GitHub
  • Re: [I] How to use hnsw int4 when loading index [lucene] via GitHub
• [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene] via GitHub
  • Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene] via GitHub
  • Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene] via GitHub
  • Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene] via GitHub
  • Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene] via GitHub
  • Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene] via GitHub
  • Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene] via GitHub
  • Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene] via GitHub
  • Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene] via GitHub
  • Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene] via GitHub
  • Re: [I] Performance difference between files getting opened with IOContext.RANDOM vs IOContext.READ during merges [lucene] via GitHub
• Re: [PR] Inter-segment I/O concurrency. [lucene] via GitHub
• Re: [PR] Use `instanceof` pattern-matching where possible [lucene] via GitHub
• [PR] Introduce multiSelect for ScalarQuantizer [lucene] via GitHub
  • Re: [PR] Introduce multiSelect for ScalarQuantizer [lucene] via GitHub
  • Re: [PR] Introduce multiSelect for ScalarQuantizer [lucene] via GitHub
  • Re: [PR] Introduce multiSelect for ScalarQuantizer [lucene] via GitHub
• [I] Speed up ScalarQuantization by selecting quantiles together [lucene] via GitHub
• Re: [PR] Skip madvise calls on tiny inner files of compound files. [lucene] via GitHub
  • Re: [PR] Skip madvise calls on tiny inner files of compound files. [lucene] via GitHub
  • Re: [PR] Skip madvise calls on tiny inner files of compound files. [lucene] via GitHub
• Re: [I] Significant performance regression with search after [lucene] via GitHub
  • Re: [I] Significant performance regression with search after [lucene] via GitHub
  • Re: [I] Significant performance regression with search after [lucene] via GitHub
  • Re: [I] Significant performance regression with search after [lucene] via GitHub
  • Re: [I] Significant performance regression with search after [lucene] via GitHub
• Re: [I] Address backward compat test issues after upgrading main to Lucene 11 [lucene] via GitHub
• Re: [PR] Forward port "Fix 9.12.0 backcompat break" to main [lucene] via GitHub
  • Re: [PR] Forward port "Fix 9.12.0 backcompat break" to main [lucene] via GitHub
• [PR] Indicate frontier init length in Lucene90BlockTreeTermsWriter#compileIndex. [lucene] via GitHub
  • Re: [PR] Indicate frontier init length in Lucene90BlockTreeTermsWriter#compileIndex. [lucene] via GitHub
• [PR] Early reset scratchBytes in Lucene90BlockTreeTermsWriter.compileIndex. [lucene] via GitHub
  • Re: [PR] Early reset scratchBytes in Lucene90BlockTreeTermsWriter.compileIndex. [lucene] via GitHub
  • Re: [PR] Early reset scratchBytes in Lucene90BlockTreeTermsWriter.compileIndex. [lucene] via GitHub
  • Re: [PR] Early reset scratchBytes in Lucene90BlockTreeTermsWriter.compileIndex. [lucene] via GitHub
  • Re: [PR] Early reset scratchBytes in Lucene90BlockTreeTermsWriter.compileIndex. [lucene] via GitHub
• Re: [PR] Remove synchronization from IndexWriter.isClosed [lucene] via GitHub
• [PR] Use multi-select instead of a full sort for DynamicRange creation [lucene] via GitHub
  • Re: [PR] Use multi-select instead of a full sort for DynamicRange creation [lucene] via GitHub
  • Re: [PR] Use multi-select instead of a full sort for DynamicRange creation [lucene] via GitHub
  • Re: [PR] Use multi-select instead of a full sort for DynamicRange creation [lucene] via GitHub
  • Re: [PR] Use multi-select instead of a full sort for DynamicRange creation [lucene] via GitHub
  • Re: [PR] Use multi-select instead of a full sort for DynamicRange creation [lucene] via GitHub
  • Re: [PR] Use multi-select instead of a full sort for DynamicRange creation [lucene] via GitHub
• [I] Support multi-tenant RAM buffers for IndexWriter [lucene] via GitHub
  • Re: [I] Support multi-tenant RAM buffers for IndexWriter [lucene] via GitHub
  • Re: [I] Support multi-tenant RAM buffers for IndexWriter [lucene] via GitHub
  • Re: [I] Support multi-tenant RAM buffers for IndexWriter [lucene] via GitHub
• [PR] Align TestGenerateBwcIndices.java with AddBackcompatindices.py [lucene] via GitHub
  • Re: [PR] Align TestGenerateBwcIndices.java with AddBackcompatindices.py [lucene] via GitHub
  • Re: [PR] Align TestGenerateBwcIndices.java with AddBackcompatindices.py [lucene] via GitHub
• [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
  • Re: [PR] Add BaseKnnVectorsFormatTestCase.testRecall() and fix old codecs [lucene] via GitHub
• [PR] Add changelog verifier [lucene] via GitHub
  • Re: [PR] Add changelog verifier [lucene] via GitHub
  • Re: [PR] Add changelog verifier [lucene] via GitHub
  • Re: [PR] Add changelog verifier [lucene] via GitHub
• [PR] Test changelog verifier [lucene] via GitHub
  • Re: [PR] Test changelog verifier [lucene] via GitHub
  • Re: [PR] Test changelog verifier [lucene] via GitHub
• Re: [I] Make dynamic range facets value collection and sorting faster [lucene] via GitHub
  • Re: [I] Make dynamic range facets value collection and sorting faster [lucene] via GitHub
  • Re: [I] Make dynamic range facets value collection and sorting faster [lucene] via GitHub
  • Re: [I] Make dynamic range facets value collection and sorting faster [lucene] via GitHub
• Re: [I] `IndexOrDocValuesQuery` does not support query highlighting [lucene] via GitHub
  • Re: [I] `IndexOrDocValuesQuery` does not support query highlighting [lucene] via GitHub
  • Re: [I] `IndexOrDocValuesQuery` does not support query highlighting [lucene] via GitHub
• [PR] Only call madvise when necessary. [lucene] via GitHub
  • Re: [PR] Only call madvise when necessary. [lucene] via GitHub
  • Re: [PR] Only call madvise when necessary. [lucene] via GitHub
  • Re: [PR] Only call madvise when necessary. [lucene] via GitHub
  • Re: [PR] Only call madvise when necessary. [lucene] via GitHub
  • Re: [PR] Only call madvise when necessary. [lucene] via GitHub
  • Re: [PR] Only call madvise when necessary. [lucene] via GitHub
  • Re: [PR] Only call madvise when necessary. [lucene] via GitHub
  • Re: [PR] Only call madvise when necessary. [lucene] via GitHub
  • Re: [PR] Only call madvise when necessary. [lucene] via GitHub
• [PR] Avoid slicing memory segments unnecessarily [lucene] via GitHub
  • Re: [PR] Avoid slicing memory segments unnecessarily [lucene] via GitHub
  • Re: [PR] Avoid slicing memory segments unnecessarily [lucene] via GitHub
  • Re: [PR] Avoid slicing memory segments unnecessarily [lucene] via GitHub
  • Re: [PR] Avoid slicing memory segments unnecessarily [lucene] via GitHub
  • Re: [PR] Avoid slicing memory segments unnecessarily [lucene] via GitHub
  • Re: [PR] Avoid slicing memory segments unnecessarily [lucene] via GitHub
  • Re: [PR] Avoid slicing memory segments unnecessarily [lucene] via GitHub
  • Re: [PR] Avoid slicing memory segments unnecessarily [lucene] via GitHub
• Re: [PR] Avoid allocating liveDocs for no soft-deletes (#13895) [lucene] via GitHub
• [PR] Remove redundant code in PointInSetQuery [lucene] via GitHub
  • Re: [PR] Remove redundant code in PointInSetQuery [lucene] via GitHub
  • Re: [PR] Remove redundant code in PointInSetQuery [lucene] via GitHub
• [PR] Better handle dynamic pruning when the leading clause has a single impact block. [lucene] via GitHub
  • Re: [PR] Better handle dynamic pruning when the leading clause has a single impact block. [lucene] via GitHub
  • Re: [PR] Better handle dynamic pruning when the leading clause has a single impact block. [lucene] via GitHub
  • Re: [PR] Better handle dynamic pruning when the leading clause has a single impact block. [lucene] via GitHub
• [PR] [SOLR-11191] SolrIndexSplitter: Init support for routing docs by _root_ when available [lucene-solr] via GitHub
  • Re: [PR] [SOLR-11191] SolrIndexSplitter: Init support for routing docs by _root_ when available [lucene-solr] via GitHub
  • Re: [PR] [SOLR-11191] SolrIndexSplitter: Init support for routing docs by _root_ when available [lucene-solr] via GitHub
  • Re: [PR] [SOLR-11191] SolrIndexSplitter: Init support for routing docs by _root_ when available [lucene-solr] via GitHub
  • Re: [PR] [SOLR-11191] SolrIndexSplitter: Init support for routing docs by _root_ when available [lucene-solr] via GitHub
  • Re: [PR] [SOLR-11191] SolrIndexSplitter: Init support for routing docs by _root_ when available [lucene-solr] via GitHub
  • Re: [PR] [SOLR-11191] SolrIndexSplitter: Init support for routing docs by _root_ when available [lucene-solr] via GitHub
  • Re: [PR] [SOLR-11191] SolrIndexSplitter: Init support for routing docs by _root_ when available [lucene-solr] via GitHub
  • Re: [PR] [SOLR-11191] SolrIndexSplitter: Init support for routing docs by _root_ when available [lucene-solr] via GitHub
  • Re: [PR] [SOLR-11191] SolrIndexSplitter: Init support for routing docs by _root_ when available [lucene-solr] via GitHub
• [PR] IndexOrDocValuesQuery in query highlighting [lucene] via GitHub
  • Re: [PR] Added support for highlighting `IndexOrDocValuesQuery` [lucene] via GitHub
  • Re: [PR] Added support for highlighting `IndexOrDocValuesQuery` [lucene] via GitHub
• Re: [I] Relax Lucene Index Upgrade Policy to Allow Safe Upgrades Across Multiple Major Versions [lucene] via GitHub
• [PR] Dry up EverythingEnum and BlockDocsEnum in Lucene912PostingsReader [lucene] via GitHub

• Earlier messages
• Later messages