issues  

Messages by Thread

• • Re: [PR] Improve hnsw on heap ram est [lucene] via GitHub
  • Re: [PR] Improve hnsw on heap ram est [lucene] via GitHub
  • Re: [PR] Improve hnsw on heap ram est [lucene] via GitHub
  • Re: [PR] Improve hnsw on heap ram est [lucene] via GitHub
  • Re: [PR] Improve hnsw on heap ram est [lucene] via GitHub
  • Re: [PR] Improve hnsw on heap ram est [lucene] via GitHub
  • Re: [PR] Improve hnsw on heap ram est [lucene] via GitHub
  • Re: [PR] Improve hnsw on heap ram est [lucene] via GitHub
  • Re: [PR] Improve hnsw on heap ram est [lucene] via GitHub
  • Re: [PR] Improve hnsw on heap ram est [lucene] via GitHub
• [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
  • Re: [PR] Build refactoring and cleanups (moving from build scripts to convention plugins) [lucene] via GitHub
• [I] Are we spending too much CPU in HNSW `ramBytesUsed`, and clearing bitsets? [lucene] via GitHub
  • Re: [I] Are we spending too much CPU in HNSW `ramBytesUsed`, and clearing bitsets? [lucene] via GitHub
  • Re: [I] Are we spending too much CPU in HNSW `ramBytesUsed`, and clearing bitsets? [lucene] via GitHub
  • Re: [I] Are we spending too much CPU in HNSW `ramBytesUsed`, and clearing bitsets? [lucene] via GitHub
  • Re: [I] Are we spending too much CPU in HNSW `ramBytesUsed`, and clearing bitsets? [lucene] via GitHub
  • Re: [I] Are we spending too much CPU in HNSW `ramBytesUsed`, and clearing bitsets? [lucene] via GitHub
  • Re: [I] Are we spending too much CPU in HNSW `ramBytesUsed`, and clearing bitsets? [lucene] via GitHub
• [PR] Add non-committer activity to activity report [lucene] via GitHub
  • Re: [PR] Add non-committer activity to activity report [lucene] via GitHub
  • Re: [PR] Add non-committer activity to activity report [lucene] via GitHub
  • Re: [PR] Add non-committer activity to activity report [lucene] via GitHub
  • Re: [PR] Add non-committer activity to activity report [lucene] via GitHub
  • Re: [PR] Add non-committer activity to activity report [lucene] via GitHub
  • Re: [PR] Add non-committer activity to activity report [lucene] via GitHub
  • Re: [PR] Add non-committer activity to activity report [lucene] via GitHub
• Re: [I] [Feature] Add support for passing extra information with KNNVectorField [lucene] via GitHub
• [PR] Convert more PriorityQueues to use Comparator [lucene] via GitHub
  • Re: [PR] Convert more PriorityQueues to use Comparator [lucene] via GitHub
  • Re: [PR] Convert more PriorityQueues to use Comparator [lucene] via GitHub
  • Re: [PR] Convert more PriorityQueues to use Comparator [lucene] via GitHub
  • Re: [PR] Convert more PriorityQueues to use Comparator [lucene] via GitHub
  • Re: [PR] Convert more PriorityQueues to use Comparator [lucene] via GitHub
  • Re: [PR] Convert more PriorityQueues to use Comparator [lucene] via GitHub
  • Re: [PR] Convert more PriorityQueues to use Comparator [lucene] via GitHub
  • Re: [PR] Convert more PriorityQueues to use Comparator [lucene] via GitHub
  • Re: [PR] Convert more PriorityQueues to use Comparator [lucene] via GitHub
• [I] bitbucket download gone for nori (mecab-ko-dic-2.1.1-20180720) [lucene] via GitHub
  • Re: [I] bitbucket download gone for nori (mecab-ko-dic-2.1.1-20180720) [lucene] via GitHub
  • Re: [I] bitbucket download gone for nori (mecab-ko-dic-2.1.1-20180720) [lucene] via GitHub
  • Re: [I] bitbucket download gone for nori (mecab-ko-dic-2.1.1-20180720) [lucene] via GitHub
  • Re: [I] bitbucket download gone for nori (mecab-ko-dic-2.1.1-20180720) [lucene] via GitHub
  • Re: [I] bitbucket download gone for nori (mecab-ko-dic-2.1.1-20180720) [lucene] via GitHub
  • Re: [I] bitbucket download gone for nori (mecab-ko-dic-2.1.1-20180720) [lucene] via GitHub
  • Re: [I] bitbucket download gone for nori (mecab-ko-dic-2.1.1-20180720) [lucene] via GitHub
  • Re: [I] bitbucket download gone for nori (mecab-ko-dic-2.1.1-20180720) [lucene] via GitHub
• Re: [I] Dynamic pruning with DocValue skipper [lucene] via GitHub
• [PR] IndexOrDocValuesQuery and IndexSortSortedNumericDocValuesRangeQuery should only be counted once when computing maxClauseCount [lucene] via GitHub
  • Re: [PR] IndexOrDocValuesQuery and IndexSortSortedNumericDocValuesRangeQuery should only be counted once when computing maxClauseCount [lucene] via GitHub
  • Re: [PR] IndexOrDocValuesQuery and IndexSortSortedNumericDocValuesRangeQuery should only be counted once when computing maxClauseCount [lucene] via GitHub
  • Re: [PR] IndexOrDocValuesQuery and IndexSortSortedNumericDocValuesRangeQuery should only be counted once when computing maxClauseCount [lucene] via GitHub
  • Re: [PR] IndexOrDocValuesQuery and IndexSortSortedNumericDocValuesRangeQuery should only be counted once when computing maxClauseCount [lucene] via GitHub
  • Re: [PR] IndexOrDocValuesQuery and IndexSortSortedNumericDocValuesRangeQuery should only be counted once when computing maxClauseCount [lucene] via GitHub
  • Re: [PR] IndexOrDocValuesQuery and IndexSortSortedNumericDocValuesRangeQuery should only be counted once when computing maxClauseCount [lucene] via GitHub
  • Re: [PR] IndexOrDocValuesQuery and IndexSortSortedNumericDocValuesRangeQuery should only be counted once when computing maxClauseCount [lucene] via GitHub
  • Re: [PR] IndexOrDocValuesQuery and IndexSortSortedNumericDocValuesRangeQuery should only be counted once when computing maxClauseCount [lucene] via GitHub
• Re: [I] QueryRescorer should be able to use the original sort on ties [lucene] via GitHub
• [I] Support multiple HNSW graphs backed by the same vectors [lucene] via GitHub
  • Re: [I] Support multiple HNSW graphs backed by the same vectors [lucene] via GitHub
  • Re: [I] Support multiple HNSW graphs backed by the same vectors [lucene] via GitHub
  • Re: [I] Support multiple HNSW graphs backed by the same vectors [lucene] via GitHub
  • Re: [I] Support multiple HNSW graphs backed by the same vectors [lucene] via GitHub
  • Re: [I] Support multiple HNSW graphs backed by the same vectors [lucene] via GitHub
  • Re: [I] Support multiple HNSW graphs backed by the same vectors [lucene] via GitHub
• Re: [I] Expand TieredMergePolicy deletePctAllowed limits [lucene] via GitHub
  • Re: [I] Expand TieredMergePolicy deletePctAllowed limits [lucene] via GitHub
  • Re: [I] Expand TieredMergePolicy deletePctAllowed limits [lucene] via GitHub
  • Re: [I] Expand TieredMergePolicy deletePctAllowed limits [lucene] via GitHub
• [PR] Fix too many documents collected when only boo-filter condition is present [lucene] via GitHub
  • Re: [PR] Fix too many documents collected when only boo-filter condition is present [lucene] via GitHub
  • Re: [PR] Fix too many documents collected when only bool-filter condition is present [lucene] via GitHub
  • Re: [PR] Fix too many documents collected when only bool-filter condition is present [lucene] via GitHub
  • Re: [PR] Fix too many documents collected when only bool-filter condition is present [lucene] via GitHub
  • Re: [PR] Fix too many documents collected when only bool-filter condition is present [lucene] via GitHub
  • Re: [PR] Fix too many documents collected when only bool-filter condition is present [lucene] via GitHub
  • Re: [PR] Fix too many documents collected when only bool-filter condition is present [lucene] via GitHub
  • Re: [PR] Fix too many documents collected when only bool-filter condition is present [lucene] via GitHub
  • Re: [PR] Fix too many documents collected when only bool-filter condition is present [lucene] via GitHub
• [I] IndexOrDocValues query is counted twice when computing `maxClauseCount` [lucene] via GitHub
  • Re: [I] IndexOrDocValuesQuery is counted twice when computing `maxClauseCount` [lucene] via GitHub
  • Re: [I] IndexOrDocValuesQuery is counted twice when computing `maxClauseCount` [lucene] via GitHub
  • Re: [I] IndexOrDocValuesQuery is counted twice when computing `maxClauseCount` [lucene] via GitHub
• [I] Too many documents collected when only boo-filter condition is present [lucene] via GitHub
  • Re: [I] Too many documents collected when only bool-filter condition is present [lucene] via GitHub
• [I] Let's explore a machine-learned MergePolicy? [lucene] via GitHub
• [PR] Implement IndexedDISI#docIDRunEnd [lucene] via GitHub
  • Re: [PR] Implement IndexedDISI#docIDRunEnd [lucene] via GitHub
  • Re: [PR] Implement IndexedDISI#docIDRunEnd [lucene] via GitHub
  • Re: [PR] Implement IndexedDISI#docIDRunEnd [lucene] via GitHub
  • Re: [PR] Implement IndexedDISI#docIDRunEnd [lucene] via GitHub
  • Re: [PR] Implement IndexedDISI#docIDRunEnd [lucene] via GitHub
  • Re: [PR] Implement IndexedDISI#docIDRunEnd [lucene] via GitHub
  • Re: [PR] Implement IndexedDISI#docIDRunEnd [lucene] via GitHub
• Re: [I] action failures sent to bui...@lucene.apache.org [lucene] via GitHub
  • Re: [I] action failures sent to bui...@lucene.apache.org [lucene] via GitHub
  • Re: [I] action failures sent to bui...@lucene.apache.org [lucene] via GitHub
  • Re: [I] action failures sent to bui...@lucene.apache.org [lucene] via GitHub
• [PR] build(deps): bump holidays from 0.71 to 0.74 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump holidays from 0.71 to 0.74 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump holidays from 0.71 to 0.74 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump holidays from 0.71 to 0.74 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump holidays from 0.71 to 0.74 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump holidays from 0.71 to 0.74 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump holidays from 0.71 to 0.74 in /dev-tools/scripts [lucene] via GitHub
• [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
  • Re: [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
  • Re: [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
  • Re: [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
  • Re: [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
  • Re: [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
  • Re: [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
  • Re: [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
  • Re: [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
  • Re: [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
  • Re: [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
  • Re: [PR] Respect minCompetitiveScore in BlockMaxConjunctionBulkScorer [lucene] via GitHub
• [PR] Add MathUtil#unsignedMin to simplify dividing the doc ID space into windows. [lucene] via GitHub
  • Re: [PR] Add MathUtil#unsignedMin to simplify dividing the doc ID space into windows. [lucene] via GitHub
• [PR] Add code comment about use of Collections#synchronizedMap in LRUQueryCache. [lucene] via GitHub
  • Re: [PR] Add code comment about use of Collections#synchronizedMap in LRUQueryCache. [lucene] via GitHub
  • Re: [PR] Add code comment about use of Collections#synchronizedMap in LRUQueryCache. [lucene] via GitHub
• Re: [PR] Dynamic pruning with DocValueSkipper [lucene] via GitHub
  • Re: [PR] Dynamic pruning with DocValueSkipper [lucene] via GitHub
  • Re: [PR] Dynamic pruning with DocValueSkipper [lucene] via GitHub
• Re: [I] Does LRUQueryCache#uniqueQueries really needs wrapped by Collections.synchronizedMap? [lucene] via GitHub
  • Re: [I] Does LRUQueryCache#uniqueQueries really needs wrapped by Collections.synchronizedMap? [lucene] via GitHub
  • Re: [I] Does LRUQueryCache#uniqueQueries really needs wrapped by Collections.synchronizedMap? [lucene] via GitHub
  • Re: [I] Does LRUQueryCache#uniqueQueries really needs wrapped by Collections.synchronizedMap? [lucene] via GitHub
  • Re: [I] Does LRUQueryCache#uniqueQueries really needs wrapped by Collections.synchronizedMap? [lucene] via GitHub
• [PR] Merge DocAndFreqBuffer and DocAndScoreBuffer. [lucene] via GitHub
  • Re: [PR] Merge DocAndFreqBuffer and DocAndScoreBuffer. [lucene] via GitHub
  • Re: [PR] Merge DocAndFreqBuffer and DocAndScoreBuffer. [lucene] via GitHub
  • Re: [PR] Merge DocAndFreqBuffer and DocAndScoreBuffer. [lucene] via GitHub
• [PR] Merge CombinedFieldQuery's WeightedDisiWrapper into DisiWrapper. [lucene] via GitHub
  • Re: [PR] Merge CombinedFieldQuery's WeightedDisiWrapper into DisiWrapper. [lucene] via GitHub
  • Re: [PR] Merge CombinedFieldQuery's WeightedDisiWrapper into DisiWrapper. [lucene] via GitHub
• [I] Can we support vectors to be loaded with direct I/O for full precision re-ranking? [lucene] via GitHub
  • Re: [I] Can we support vectors to be loaded with direct I/O for full precision re-ranking? [lucene] via GitHub
• Re: [PR] deps(java): bump org.apache.rat:apache-rat from 0.14 to 0.16.1 [lucene] via GitHub
  • Re: [PR] deps(java): bump org.apache.rat:apache-rat from 0.14 to 0.16.1 [lucene] via GitHub
• [PR] build(deps): bump holidays from 0.71 to 0.73 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump holidays from 0.71 to 0.73 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump holidays from 0.71 to 0.73 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump holidays from 0.71 to 0.73 in /dev-tools/scripts [lucene] via GitHub
• [PR] build(deps): bump basedpyright from 1.29.1 to 1.29.2 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump basedpyright from 1.29.1 to 1.29.2 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump basedpyright from 1.29.1 to 1.29.2 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump basedpyright from 1.29.1 to 1.29.2 in /dev-tools/scripts [lucene] via GitHub
• [PR] build(deps): bump ruff from 0.11.9 to 0.11.12 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump ruff from 0.11.9 to 0.11.12 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump ruff from 0.11.9 to 0.11.12 in /dev-tools/scripts [lucene] via GitHub
• [PR] Fix: Include tests.jvmargs in "Reproduce with" output [lucene] via GitHub
  • Re: [PR] Fix: Include tests.jvmargs in "Reproduce with" output [lucene] via GitHub
  • Re: [PR] Fix: Include tests.jvmargs in "Reproduce with" output [lucene] via GitHub
  • Re: [PR] Fix: Include tests.jvmargs in "Reproduce with" output [lucene] via GitHub
• [I] Failing test: TestSpellChecking.testGeneratedSuggestions — ComparisonFailure with expected suggestion list [lucene] via GitHub
  • Re: [I] Failing test: TestSpellChecking.testGeneratedSuggestions — ComparisonFailure with expected suggestion list [lucene] via GitHub
  • Re: [I] Failing test: TestSpellChecking.testGeneratedSuggestions — ComparisonFailure with expected suggestion list [lucene] via GitHub

• Earlier messages
• Later messages