issues  

Messages by Thread

• • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
  • Re: [PR] Added shared prefetch counter [lucene] via GitHub
• [PR] Compute 'length' of fields with custom term frequencies as docFreq [lucene] via GitHub
  • Re: [PR] Compute 'length' of fields with custom term frequencies as docFreq [lucene] via GitHub
  • Re: [PR] Compute 'length' of fields with custom term frequencies as docFreq [lucene] via GitHub
  • Re: [PR] Compute 'length' of fields with custom term frequencies as docFreq [lucene] via GitHub
  • Re: [PR] Compute 'length' of fields with custom term frequencies as docFreq [lucene] via GitHub
  • Re: [PR] Compute 'length' of fields with custom term frequencies as docFreq [lucene] via GitHub
  • Re: [PR] Compute 'length' of fields with custom term frequencies as docFreq [lucene] via GitHub
  • Re: [PR] Compute 'length' of fields with custom term frequencies as docFreq [lucene] via GitHub
  • Re: [PR] Compute 'length' of fields with custom term frequencies as docFreq [lucene] via GitHub
  • Re: [PR] Compute 'length' of fields with custom term frequencies as docFreq [lucene] via GitHub
• [I] Bypass total frequency check if field uses custom term frequency [LUCENE-10048] [lucene] via GitHub
  • Re: [I] Bypass total frequency check if field uses custom term frequency [LUCENE-10048] [lucene] via GitHub
• Re: [I] Use @snippet javadoc tag for snippets [lucene] via GitHub
  • Re: [I] Use @snippet javadoc tag for snippets [lucene] via GitHub
• [PR] Make intellij think vector module is imported for mrjar/java25 module [lucene] via GitHub
  • Re: [PR] Make intellij think vector module is imported for mrjar/java25 module [lucene] via GitHub
  • Re: [PR] Make intellij think vector module is imported for mrjar/java25 module [lucene] via GitHub
  • Re: [PR] Make intellij think vector module is imported for mrjar/java25 module [lucene] via GitHub
  • Re: [PR] Make intellij think vector module is imported for mrjar/java25 module [lucene] via GitHub
• [PR] Avoid copying bitset that's subsequently cleared [lucene] via GitHub
  • Re: [PR] Avoid copying bitset that's subsequently cleared [lucene] via GitHub
  • Re: [PR] Avoid copying bitset that's subsequently cleared [lucene] via GitHub
  • Re: [PR] Avoid copying bitset that's subsequently cleared [lucene] via GitHub
  • Re: [PR] Avoid copying bitset that's subsequently cleared [lucene] via GitHub
  • Re: [PR] Avoid copying bitset that's subsequently cleared [lucene] via GitHub
• [PR] Minor javadoc clarification to HasIndexSlice::getSlice [lucene] via GitHub
  • Re: [PR] Minor javadoc clarification that HasIndexSlice::getSlice can return null [lucene] via GitHub
• [I] Failure in TestAddIndexes.testAddIndexesWithConcurrentMerges [lucene] via GitHub
• [I] Should we support preloading slices of MemorySegmentIndexInput? [lucene] via GitHub
  • Re: [I] Should we support preloading slices of MemorySegmentIndexInput? [lucene] via GitHub
• [PR] Fix dibit striping for quantized vector formats [lucene] via GitHub
  • Re: [PR] Fix dibit striping for quantized vector formats [lucene] via GitHub
• [PR] Minor matches highlighter optimizations [lucene] via GitHub
  • Re: [PR] Minor matches highlighter optimizations [lucene] via GitHub
• [I] TestLucene104ScalarQuantizedVectorsFormat.testReadQuantizedVectorWithEmptyRawVectors failures [lucene] via GitHub
  • Re: [I] TestLucene104ScalarQuantizedVectorsFormat.testReadQuantizedVectorWithEmptyRawVectors failures [lucene] via GitHub
  • Re: [I] TestLucene104ScalarQuantizedVectorsFormat.testReadQuantizedVectorWithEmptyRawVectors failures [lucene] via GitHub
  • Re: [I] TestLucene104ScalarQuantizedVectorsFormat.testReadQuantizedVectorWithEmptyRawVectors failures [lucene] via GitHub
  • Re: [I] TestLucene104ScalarQuantizedVectorsFormat.testReadQuantizedVectorWithEmptyRawVectors failures [lucene] via GitHub
  • Re: [I] TestLucene104ScalarQuantizedVectorsFormat.testReadQuantizedVectorWithEmptyRawVectors failures [lucene] via GitHub
• [PR] Replace the deprecated usage of search(Query, Collector) in core [lucene] via GitHub
  • Re: [PR] Replace the deprecated usage of search(Query, Collector) in core [lucene] via GitHub
• [PR] Introduce FirstPassGroupingCollectorManager [lucene] via GitHub
  • Re: [PR] Introduce FirstPassGroupingCollectorManager [lucene] via GitHub
• [PR] Replace prettyprint with code tag for prism. [lucene] via GitHub
  • Re: [PR] Replace prettyprint with code tag for prism. [lucene] via GitHub
  • Re: [PR] Replace prettyprint with code tag for prism. [lucene] via GitHub
• [I] Should we increase `BufferedChecksum`'s buffer from 1 KB -> 2 KB? [lucene] via GitHub
  • Re: [I] Should we increase `BufferedChecksum`'s buffer from 1 KB -> 2 KB? [lucene] via GitHub
  • Re: [I] Should we increase `BufferedChecksum`'s buffer from 1 KB -> 2 KB? [lucene] via GitHub
  • Re: [I] Should we increase `BufferedChecksum`'s buffer from 1 KB -> 2 KB? [lucene] via GitHub
  • Re: [I] Should we increase `BufferedChecksum`'s buffer from 1 KB -> 2 KB? [lucene] via GitHub
  • Re: [I] Should we increase `BufferedChecksum`'s buffer from 1 KB -> 2 KB? [lucene] via GitHub
  • Re: [I] Should we increase `BufferedChecksum`'s buffer from 1 KB -> 2 KB? [lucene] via GitHub
  • Re: [I] Should we increase `BufferedChecksum`'s buffer from 1 KB -> 2 KB? [lucene] via GitHub
• [I] Share prefetch hit counter across slices/clones [lucene] via GitHub
  • Re: [I] Share prefetch hit counter across slices/clones [lucene] via GitHub
  • Re: [I] Share prefetch hit counter across slices/clones [lucene] via GitHub
  • Re: [I] Share prefetch hit counter across slices/clones [lucene] via GitHub
• [PR] Fix offset 0 handling by LZ4 decompression [lucene] via GitHub
  • Re: [PR] Fix offset 0 handling by LZ4 decompression [lucene] via GitHub
  • Re: [PR] Fix offset 0 handling by LZ4 decompression [lucene] via GitHub
  • Re: [PR] Fix offset 0 handling by LZ4 decompression [lucene] via GitHub
  • Re: [PR] Fix offset 0 handling by LZ4 decompression [lucene] via GitHub
  • Re: [PR] Fix offset 0 handling by LZ4 decompression [lucene] via GitHub
  • Re: [PR] Fix offset 0 handling by LZ4 decompression [lucene] via GitHub
  • Re: [PR] Fix offset 0 handling by LZ4 decompression [lucene] via GitHub
  • Re: [PR] Fix offset 0 handling by LZ4 decompression [lucene] via GitHub
  • Re: [PR] Fix offset 0 handling by LZ4 decompression [lucene] via GitHub
  • Re: [PR] Disallow invalid offset 0 for LZ4 decompression [lucene] via GitHub
  • Re: [PR] Disallow invalid offset 0 for LZ4 decompression [lucene] via GitHub
  • Re: [PR] Disallow invalid offset 0 for LZ4 decompression [lucene] via GitHub
  • Re: [PR] Disallow invalid offset 0 for LZ4 decompression [lucene] via GitHub
  • Re: [PR] Disallow invalid offset 0 for LZ4 decompression [lucene] via GitHub
  • Re: [PR] Disallow invalid offset 0 for LZ4 decompression [lucene] via GitHub
  • Re: [PR] Disallow invalid offset 0 for LZ4 decompression [lucene] via GitHub
  • Re: [PR] Disallow invalid offset 0 for LZ4 decompression [lucene] via GitHub
• [PR] Allow a DataAccessHint to be passed during the construction of a Lucene99FlatVectorsReader [lucene] via GitHub
  • Re: [PR] Allow a DataAccessHint to be passed during the construction of a Lucene99FlatVectorsReader [lucene] via GitHub
• [PR] Add markdown support for javadocs and modernize highlighting a bit. [lucene] via GitHub
  • Re: [PR] Add markdown support for javadocs and modernize highlighting a bit. [lucene] via GitHub
• Re: [PR] Introduced OffHeapQuantizedFloatVectorValues class to access float vectors when only quantized byte vectors are available in the index [lucene] via GitHub
  • Re: [PR] Introduced OffHeapQuantizedFloatVectorValues class to access float vectors when only quantized byte vectors are available in the index [lucene] via GitHub
  • Re: [PR] Introduced OffHeapQuantizedFloatVectorValues class to access float vectors when only quantized byte vectors are available in the index [lucene] via GitHub
  • Re: [PR] Introduced OffHeapQuantizedFloatVectorValues class to access float vectors when only quantized byte vectors are available in the index [lucene] via GitHub
• Re: [PR] Reduce bloom filter size by using the optimal count for hash functions. [lucene] via GitHub
  • Re: [PR] Reduce bloom filter size by using the optimal count for hash functions. [lucene] via GitHub
  • Re: [PR] Reduce bloom filter size by using the optimal count for hash functions. [lucene] via GitHub
  • Re: [PR] Reduce bloom filter size by using the optimal count for hash functions. [lucene] via GitHub
  • Re: [PR] Reduce bloom filter size by using the optimal count for hash functions. [lucene] via GitHub
  • Re: [PR] Reduce bloom filter size by using the optimal count for hash functions. [lucene] via GitHub
  • Re: [PR] Reduce bloom filter size by using the optimal count for hash functions. [lucene] via GitHub
  • Re: [PR] Reduce bloom filter size by using the optimal count for hash functions. [lucene] via GitHub
  • Re: [PR] Reduce bloom filter size by using the optimal count for hash functions. [lucene] via GitHub
• [PR] Upgrade to gradle 9.2.1 [lucene] via GitHub
  • Re: [PR] Upgrade to gradle 9.2.1 [lucene] via GitHub
• [PR] Sync github workflow changes with the main branch [lucene] via GitHub
  • Re: [PR] Sync github workflow changes with the main branch [lucene] via GitHub
  • Re: [PR] Sync github workflow changes with the main branch [lucene] via GitHub
• Re: [PR] [WIP] Explore ART. [lucene] via GitHub
• [PR] Introduce AllGroupHeadsCollectorManager [lucene] via GitHub
  • Re: [PR] Introduce AllGroupHeadsCollectorManager [lucene] via GitHub
• [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
  • Re: [PR] Two bit quantization for dense vectors [lucene] via GitHub
• [PR] test: mark horribly slow tests with @Nightly [lucene] via GitHub
  • Re: [PR] Backport: mark horribly slow tests with @Nightly [lucene] via GitHub
• [PR] support flat mode [lucene] via GitHub
  • Re: [PR] support flat mode [lucene] via GitHub
• Re: [I] UAX29URLEmailTokenizerImpl.jflex matches emails with commas and invalid periods in the local part [lucene] via GitHub
• [I] AcceptDocs#cost() fully consumes iterator, invalidating any possible perf gain [lucene] via GitHub
  • Re: [I] AcceptDocs#cost() fully consumes iterator, invalidating any possible perf gain [lucene] via GitHub
  • Re: [I] AcceptDocs#cost() fully consumes iterator, invalidating any possible perf gain [lucene] via GitHub
  • Re: [I] AcceptDocs#cost() fully consumes iterator, invalidating any possible perf gain [lucene] via GitHub
  • Re: [I] AcceptDocs#cost() fully consumes iterator, invalidating any possible perf gain [lucene] via GitHub
  • Re: [I] AcceptDocs#cost() fully consumes iterator, invalidating any possible perf gain [lucene] via GitHub
  • Re: [I] AcceptDocs#cost() fully consumes iterator, invalidating any possible perf gain [lucene] via GitHub
  • Re: [I] AcceptDocs#cost() fully consumes iterator, invalidating any possible perf gain [lucene] via GitHub
  • Re: [I] AcceptDocs#cost() fully consumes iterator, invalidating any possible perf gain [lucene] via GitHub
• [PR] Avoid unnecessary getGraph() call [lucene] via GitHub
  • Re: [PR] Avoid unnecessary getGraph() call [lucene] via GitHub
  • Re: [PR] Avoid unnecessary getGraph() call [lucene] via GitHub
  • Re: [PR] Avoid unnecessary getGraph() call [lucene] via GitHub
  • Re: [PR] Avoid unnecessary getGraph() call [lucene] via GitHub
  • Re: [PR] Avoid unnecessary getGraph() call [lucene] via GitHub
• [PR] Deprecate some public FuzzySet methods ahead of removing them in a future release [lucene] via GitHub
  • Re: [PR] Deprecate some public FuzzySet methods ahead of removing them in a future release [lucene] via GitHub
• [PR] Refactor QueryCache to improve performance [lucene] via GitHub
  • Re: [PR] Refactor QueryCache to improve performance [lucene] via GitHub
  • Re: [PR] Refactor QueryCache to improve performance [lucene] via GitHub
  • Re: [PR] Refactor QueryCache to improve performance [lucene] via GitHub
  • Re: [PR] Refactor QueryCache to improve performance [lucene] via GitHub
  • Re: [PR] Refactor QueryCache to improve performance [lucene] via GitHub
  • Re: [PR] Refactor QueryCache to improve performance [lucene] via GitHub
  • Re: [PR] Refactor QueryCache to improve performance [lucene] via GitHub
  • Re: [PR] Refactor QueryCache to improve performance [lucene] via GitHub
  • Re: [PR] Refactor QueryCache to improve performance [lucene] via GitHub
  • Re: [PR] Refactor QueryCache to improve performance [lucene] via GitHub
  • Re: [PR] Refactor QueryCache to improve performance [lucene] via GitHub
• [PR] Introduce AllGroupsCollectorManager [lucene] via GitHub
  • Re: [PR] Introduce AllGroupsCollectorManager [lucene] via GitHub
  • Re: [PR] Introduce AllGroupsCollectorManager [lucene] via GitHub
• [PR] Adaptive index mode [lucene] via GitHub
  • Re: [PR] Adaptive indexing mode for prefetching [lucene] via GitHub
  • Re: [PR] Adaptive indexing mode for prefetching [lucene] via GitHub
  • Re: [PR] Adaptive indexing mode for prefetching [lucene] via GitHub
  • Re: [PR] Adaptive indexing mode for prefetching [lucene] via GitHub
  • Re: [PR] Adaptive indexing mode for prefetching [lucene] via GitHub
  • Re: [PR] Adaptive indexing mode for prefetching [lucene] via GitHub
• [PR] Add comment in SegmentTermsEnum#seekCeil/Exact. [lucene] via GitHub
  • Re: [PR] Add comment in SegmentTermsEnum#seekCeil/Exact. [lucene] via GitHub
• [I] Unable to Tessellate shape for valid Polygon [lucene] via GitHub
• Re: [I] MergedByteVectorValues is missing increasing `lastOrd` when advancing. [lucene] via GitHub
• [PR] Fix mergedbytevectorvalues lastord [lucene] via GitHub
  • Re: [PR] Fix mergedbytevectorvalues lastord [lucene] via GitHub
  • Re: [PR] Fix mergedbytevectorvalues lastord [lucene] via GitHub
  • Re: [PR] Fix mergedbytevectorvalues lastord [lucene] via GitHub
  • Re: [PR] Fix mergedbytevectorvalues lastord [lucene] via GitHub
• [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub
  • Re: [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub
  • Re: [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub
  • Re: [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub
  • Re: [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub
  • Re: [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub
  • Re: [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub
  • Re: [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub
  • Re: [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub
  • Re: [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub
  • Re: [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub
  • Re: [I] Provide helper utility API to compute CRC32 across concurrent (map/reduce) chunks [lucene] via GitHub

• Earlier messages
• Later messages