issues  

Messages by Thread

• Re: [PR] LUCENE-10333: Speed up BinaryDocValues with a batch reading on LongValues [lucene] via GitHub
• Re: [PR] Remove redundant code in Lucene search [lucene] via GitHub
• Re: [PR] Compute multiple float aggregations in one go [lucene] via GitHub
• Re: [PR] Fix onlyLongestMatch in DictionaryCompoundWordTokenFilter [lucene] via GitHub
• Re: [PR] Improve exception handling for readLongs/readInts/readFloats in ByteBufferIndexInput [lucene] via GitHub
• Re: [PR] LUCENE-10334: Introduce a BlockReader based on ForUtil and use it for NumericDocValues [lucene] via GitHub
• Re: [PR] LUCENE-10616: optimizing decompress when only retrieving some fields [lucene] via GitHub
• Re: [PR] Remove synchronization from OpenNLP integration and add thread-safety tests(checkRandomData) [lucene] via GitHub
• Re: [PR] Exclude words ending in -ion from Swedish minimal and light stemmers. [lucene] via GitHub
• Re: [PR] Improve refresh speed with softdelete enable [lucene] via GitHub
• Re: [PR] During concurrent slice searches in IndexSearcher stop other tasks if one throws an Exception [lucene] via GitHub
• Re: [PR] clean up smoketester GPG leaks [lucene] via GitHub
• Re: [PR] Throw CorruptSegmentInfoException on encountering missing segment info (_N.si) file in CheckIndex [lucene] via GitHub
• Re: [PR] Add Facets#getBulkSpecificValues method [lucene] via GitHub
• Re: [PR] Bump Yetus version to 0.15.0 [lucene] via GitHub
• Re: [PR] Add support for querying multiple fields to QueryBuilder. [lucene] via GitHub
• Re: [PR] Vector accelerated GroupVInt decoder for MemorySegmentIndexInput [lucene] via GitHub
• Re: [PR] nocommit: demonstrate how a minor change in IndexSearcher can have an inexplicable performance impact [lucene] via GitHub
• Re: [PR] Optimize binary search call [lucene] via GitHub
• Re: [PR] Allow reading binary doc values as a RandomAccessInput [lucene] via GitHub
• Re: [PR] Remove usage of IndexSearcher#search(Query, Collector) from join package [lucene] via GitHub
• Re: [PR] [Bug] Fix for postings force merge regression [lucene] via GitHub
• Re: [PR] Pruning of estimating the point value count in BooleanScorerSupplier [lucene] via GitHub
• Re: [PR] feat(nori): add metadata support to Korean tokenizer [lucene] via GitHub
• Re: [PR] Add AcceptDocs abstraction for accepted KNN docs [lucene] via GitHub
  • Re: [PR] Add AcceptDocs abstraction for accepted KNN docs [lucene] via GitHub
  • Re: [PR] Add AcceptDocs abstraction for accepted KNN docs [lucene] via GitHub
• [PR] Run the tests with assertions disabled ~25% of the time [lucene] via GitHub
  • Re: [PR] Run the tests with assertions disabled ~25% of the time [lucene] via GitHub
• [PR] Fix potential NPE for KnnVectorQuery [lucene] via GitHub
  • Re: [PR] Fix potential NPE for KnnVectorQuery [lucene] via GitHub
  • Re: [PR] Fix potential NPE for KnnVectorQuery [lucene] via GitHub
  • Re: [PR] Fix potential NPE for KnnVectorQuery [lucene] via GitHub
  • Re: [PR] Fix potential NPE for KnnVectorQuery [lucene] via GitHub
  • Re: [PR] Fix potential NPE for KnnVectorQuery [lucene] via GitHub
  • Re: [PR] Fix potential NPE for KnnVectorQuery [lucene] via GitHub
  • Re: [PR] Fix potential NPE for KnnVectorQuery [lucene] via GitHub
• [I] Highlighter.getBestFragments() merges zero-scored fragments with scored fragments, polluting highlight results [lucene] via GitHub
• [PR] Solve the problem of excessive memory usage in ultra-long text search case [lucene] via GitHub
  • Re: [PR] Solve the problem of excessive memory usage in ultra-long text search case [lucene] via GitHub
  • Re: [PR] Solve the problem of excessive memory usage in ultra-long text search case [lucene] via GitHub
  • Re: [PR] Solve the problem of excessive memory usage in ultra-long text search case [lucene] via GitHub
  • Re: [PR] Solve the problem of excessive memory usage in ultra-long text search case [lucene] via GitHub
  • Re: [PR] Solve the problem of excessive memory usage in ultra-long text search case [lucene] via GitHub
  • Re: [PR] Add PhraseQuery.Builder.setMaxTerms() method to limit the maximum number of terms and excessive memory use [lucene] via GitHub
  • Re: [PR] Add PhraseQuery.Builder.setMaxTerms() method to limit the maximum number of terms and excessive memory use [lucene] via GitHub
• [PR] fix(apache#15309): Optimize PriorityQueue.remove() function [lucene] via GitHub
  • Re: [PR] fix(apache#15309): Optimize PriorityQueue.remove() function [lucene] via GitHub
  • Re: [PR] fix(apache#15309): Optimize PriorityQueue.remove() function [lucene] via GitHub
  • Re: [PR] fix(apache#15309): Optimize PriorityQueue.remove() function [lucene] via GitHub
  • Re: [PR] fix(apache#15309): Optimize PriorityQueue.remove() function [lucene] via GitHub
  • Re: [PR] fix(apache#15309): Optimize PriorityQueue.remove() function [lucene] via GitHub
  • Re: [PR] fix(apache#15309): Optimize PriorityQueue.remove() function [lucene] via GitHub
  • Re: [PR] fix(apache#15309): Optimize PriorityQueue.remove() function [lucene] via GitHub
  • Re: [PR] fix(apache#15309): Optimize PriorityQueue.remove() function [lucene] via GitHub
  • Re: [PR] fix(apache#15309): Optimize PriorityQueue.remove() function [lucene] via GitHub
• [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
  • Re: [PR] Add matomo tracker for javadoc [lucene] via GitHub
• [I] Batch together virtual calls in BKDReader for CELL_CROSSES_QUERY case? [lucene] via GitHub
  • Re: [I] Batch together virtual calls in BKDReader for CELL_CROSSES_QUERY case? [lucene] via GitHub
• [PR] build: gradle seems to not run error-prone [lucene] via GitHub
  • Re: [PR] build: gradle seems to not run error-prone [lucene] via GitHub
  • Re: [PR] build: gradle seems to not run error-prone [lucene] via GitHub
  • Re: [PR] build: gradle seems to not run error-prone [lucene] via GitHub
  • Re: [PR] build: gradle seems to not run error-prone [lucene] via GitHub
  • Re: [PR] build: gradle seems to not run error-prone [lucene] via GitHub
  • Re: [PR] build: gradle seems to not run error-prone [lucene] via GitHub
  • Re: [PR] build: gradle seems to not run error-prone [lucene] via GitHub
• [PR] Avoid static dependency from TermsEnum to one of its subclasses [lucene] via GitHub
  • Re: [PR] Avoid static dependency from TermsEnum to one of its subclasses [lucene] via GitHub
  • Re: [PR] Avoid static dependency from TermsEnum to one of its subclasses [lucene] via GitHub
  • Re: [PR] Avoid static dependency from TermsEnum to one of its subclasses [lucene] via GitHub
  • Re: [PR] Avoid static dependency from TermsEnum to one of its subclasses [lucene] via GitHub
  • Re: [PR] Avoid static dependency from TermsEnum to one of its subclasses [lucene] via GitHub
  • Re: [PR] Avoid static dependency from TermsEnum to one of its subclasses [lucene] via GitHub
  • Re: [PR] Avoid static dependency from TermsEnum to one of its subclasses [lucene] via GitHub
  • Re: [PR] Avoid static dependency from TermsEnum to one of its subclasses [lucene] via GitHub
  • Re: [PR] Avoid static dependency from TermsEnum to one of its subclasses [lucene] via GitHub
• [PR] Prevent zero radius in BaseXYPointTestCase [lucene] via GitHub
  • Re: [PR] Prevent zero radius in BaseXYPointTestCase [lucene] via GitHub
  • Re: [PR] Prevent zero radius in BaseXYPointTestCase [lucene] via GitHub
• [PR] test: remove slow test for java 21 bug [lucene] via GitHub
  • Re: [PR] test: remove slow test for java 21 bug [lucene] via GitHub
  • Re: [PR] test: remove slow test for java 21 bug [lucene] via GitHub
  • Re: [PR] test: remove slow test for java 21 bug [lucene] via GitHub
• [I] PriorityQueue.remove should be removed or improved [lucene] via GitHub
  • Re: [I] PriorityQueue.remove should be removed or improved [lucene] via GitHub
• [PR] Update forbiddenapis to v3.10 and remove hack required to use Java 25 [lucene] via GitHub
  • Re: [PR] Update forbiddenapis to v3.10 and remove hack required to use Java 25 [lucene] via GitHub
  • Re: [PR] Update forbiddenapis to v3.10 and remove hack required to use Java 25 [lucene] via GitHub
  • Re: [PR] Update forbiddenapis to v3.10 and remove hack required to use Java 25 [lucene] via GitHub
  • Re: [PR] Update forbiddenapis to v3.10 and remove hack required to use Java 25 [lucene] via GitHub
  • Re: [PR] Update forbiddenapis to v3.10 and remove hack required to use Java 25 [lucene] via GitHub
• [PR] update _footer.html - "Apache and the Apache [feather ]logo ..." [lucene-site] via GitHub
  • Re: [PR] update _footer.html - "Apache and the Apache [feather ]logo ..." [lucene-site] via GitHub
• [PR] Replace conditional logic in add(), subtract() with bit manipulation [lucene] via GitHub
  • Re: [PR] Replace conditional logic in add(), subtract() with bit manipulation [lucene] via GitHub
  • Re: [PR] Replace conditional logic in add(), subtract() with bit manipulation [lucene] via GitHub
  • Re: [PR] Replace conditional logic in add(), subtract() with bit manipulation [lucene] via GitHub
• [PR] deps(java): bump com.diffplug.spotless from 7.2.1 to 8.0.0 [lucene] via GitHub
  • Re: [PR] deps(java): bump com.diffplug.spotless from 7.2.1 to 8.0.0 [lucene] via GitHub
• [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
  • Re: [PR] Separate Panama and Vector classes [lucene] via GitHub
• [I] Should we separate Panama and Vectorization classes? [lucene] via GitHub
  • Re: [I] Should we separate Panama and Vectorization classes? [lucene] via GitHub
• [PR] Move legacy scalar formats to backwards_codecs [lucene] via GitHub
  • Re: [PR] Move legacy scalar formats to backwards_codecs [lucene] via GitHub
  • Re: [PR] Move legacy scalar formats to backwards_codecs [lucene] via GitHub
  • Re: [PR] Move legacy scalar formats to backwards_codecs [lucene] via GitHub
  • Re: [PR] Move legacy scalar formats to backwards_codecs [lucene] via GitHub
  • Re: [PR] Move legacy scalar formats to backwards_codecs [lucene] via GitHub
  • Re: [PR] Move legacy scalar formats to backwards_codecs [lucene] via GitHub
  • Re: [PR] Move legacy scalar formats to backwards_codecs [lucene] via GitHub
  • Re: [PR] Move legacy scalar formats to backwards_codecs [lucene] via GitHub
  • Re: [PR] Move legacy scalar formats to backwards_codecs [lucene] via GitHub
  • Re: [PR] Move legacy scalar formats to backwards_codecs [lucene] via GitHub
• [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
  • Re: [PR] [10.3] Fix returned Impacts when frequencies are not indexed [lucene] via GitHub
• [I] Eclipse configuration doesn't work [lucene] via GitHub
  • Re: [I] Eclipse configuration doesn't work [lucene] via GitHub
  • Re: [I] Eclipse configuration doesn't work [lucene] via GitHub
  • Re: [I] Eclipse configuration doesn't work [lucene] via GitHub
  • Re: [I] Eclipse configuration doesn't work [lucene] via GitHub
  • Re: [I] Eclipse configuration doesn't work [lucene] via GitHub
  • Re: [I] Eclipse configuration doesn't work [lucene] via GitHub
  • Re: [I] Eclipse configuration doesn't work [lucene] via GitHub
  • Re: [I] Eclipse configuration doesn't work [lucene] via GitHub
  • Re: [I] Eclipse configuration doesn't work [lucene] via GitHub
  • Re: [I] Eclipse configuration doesn't work [lucene] via GitHub
• [PR] build(deps): bump holidays from 0.80 to 0.81 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump holidays from 0.80 to 0.81 in /dev-tools/scripts [lucene] via GitHub
• [PR] ci: bump actions/stale from 9.1.0 to 10.0.0 [lucene] via GitHub
  • Re: [PR] ci: bump actions/stale from 9.1.0 to 10.0.0 [lucene] via GitHub
• [PR] ci: bump astral-sh/setup-uv from 6.7.0 to 6.8.0 [lucene] via GitHub
  • Re: [PR] ci: bump astral-sh/setup-uv from 6.7.0 to 6.8.0 [lucene] via GitHub
• [PR] build(deps): bump pygithub from 2.7.0 to 2.8.1 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump pygithub from 2.7.0 to 2.8.1 in /dev-tools/scripts [lucene] via GitHub
• [PR] ci: bump github/codeql-action from 3.30.3 to 3.30.5 [lucene] via GitHub
  • Re: [PR] ci: bump github/codeql-action from 3.30.3 to 3.30.5 [lucene] via GitHub
• [PR] build(deps): bump ruff from 0.12.11 to 0.13.2 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump ruff from 0.12.11 to 0.13.2 in /dev-tools/scripts [lucene] via GitHub
• [PR] ci: bump actions/labeler from 5.0.0 to 6.0.1 [lucene] via GitHub
  • Re: [PR] ci: bump actions/labeler from 5.0.0 to 6.0.1 [lucene] via GitHub
  • Re: [PR] ci: bump actions/labeler from 5.0.0 to 6.0.1 [lucene] via GitHub
• [PR] ci: bump gradle/actions from 4.4.4 to 5.0.0 [lucene] via GitHub
  • Re: [PR] ci: bump gradle/actions from 4.4.4 to 5.0.0 [lucene] via GitHub
• [PR] Performance regression in vector computations due to call site pollution [lucene] via GitHub
  • Re: [PR] Performance regression in vector computations due to call site pollution [lucene] via GitHub
  • Re: [PR] Performance regression in vector computations due to call site pollution [lucene] via GitHub
  • Re: [PR] Performance regression in vector computations due to call site pollution [lucene] via GitHub
  • Re: [PR] Performance regression in vector computations due to call site pollution [lucene] via GitHub
  • Re: [PR] Performance regression in vector computations due to call site pollution [lucene] via GitHub
  • Re: [PR] Performance regression in vector computations due to call site pollution [lucene] via GitHub
  • Re: [PR] Performance regression in vector computations due to call site pollution [lucene] via GitHub
  • Re: [PR] Performance regression in vector computations due to call site pollution [lucene] via GitHub
• Re: [PR] developer.md - add gitbox.apache.org clone option [lucene-site] via GitHub
• [PR] Extend Lucene104ScalarQuantization format to support quant asymmetry [lucene] via GitHub
  • Re: [PR] Extend Lucene104ScalarQuantization format to support quant asymmetry [lucene] via GitHub
  • Re: [PR] Extend Lucene104ScalarQuantization format to support quant asymmetry [lucene] via GitHub
  • Re: [PR] Extend Lucene104ScalarQuantization format to support quant asymmetry [lucene] via GitHub
  • Re: [PR] Extend Lucene104ScalarQuantization format to support quant asymmetry [lucene] via GitHub
  • Re: [PR] Extend Lucene104ScalarQuantization format to support quant asymmetry [lucene] via GitHub
  • Re: [PR] Extend Lucene104ScalarQuantization format to support quant asymmetry [lucene] via GitHub
  • Re: [PR] Extend Lucene104ScalarQuantization format to support quant asymmetry [lucene] via GitHub

• Earlier messages
• Later messages