issues  

Messages by Thread

• • 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
  • 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
  • Re: [PR] Fix mergedbytevectorvalues lastord [lucene] via GitHub
• Re: [PR] [QueryCache] Use RamUsageEstimator instead of defaulting to 1024 bytes for non-accountable query size [lucene] via GitHub
• Re: [PR] Update TermStates.java to remove deferred lambda in TermStates.get [lucene] via GitHub
  • Re: [PR] Update TermStates.java to remove deferred lambda in TermStates.get [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
  • 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: [PR] Expose MergeRateLimiter in runOnMergeFinished hook [lucene] via GitHub
  • Re: [PR] Expose MergeRateLimiter in runOnMergeFinished hook [lucene] via GitHub
• Re: [PR] Enforce fallback support for float vector retrieval in quantized KNN vector formats [lucene] via GitHub
  • Re: [PR] Enforce fallback support for float vector retrieval in quantized KNN vector formats [lucene] via GitHub
  • Re: [PR] Enforce fallback support for float vector retrieval in quantized KNN vector formats [lucene] via GitHub
  • Re: [PR] Enforce fallback support for float vector retrieval in quantized KNN vector formats [lucene] via GitHub
• [PR] ci: pin unpinned actions ref [lucene] via GitHub
  • Re: [PR] ci: pin unpinned actions ref [lucene] via GitHub
• [PR] Use Google's maven central mirror on github runners [lucene] via GitHub
  • Re: [PR] Use Google's maven central mirror on github runners [lucene] via GitHub
  • Re: [PR] Use Google's maven central mirror on github runners [lucene] via GitHub
  • Re: [PR] Use Google's maven central mirror on github runners [lucene] via GitHub
  • Re: [PR] Use Google's maven central mirror on github runners [lucene] via GitHub
  • Re: [PR] Use Google's maven central mirror on github runners [lucene] via GitHub
  • Re: [PR] Use Google's maven central mirror on github runners [lucene] via GitHub
• Re: [I] Should we rewrite/optimize the HNSW graph in 2nd pass? [lucene] via GitHub
• Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
  • Re: [PR] Align vectors on disk for optimal performance on ARM CPUs [lucene] via GitHub
• Re: [I] Highlighter QueryPhraseMap boost overridden due to conflicting query expansion [lucene] via GitHub
• Re: [I] Should we add bfloat16 support for HNSW? [lucene] via GitHub
• [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
  • Re: [PR] Add half-float (FP16) storage support for vectors [lucene] via GitHub
• Re: [PR] Fix QueryPhraseMap.markTerminal() boost override due to conflicting query expansion [lucene] via GitHub
  • Re: [PR] Fix QueryPhraseMap.markTerminal() boost override due to conflicting query expansion [lucene] via GitHub
  • Re: [PR] Fix QueryPhraseMap.markTerminal() boost override due to conflicting query expansion [lucene] via GitHub
  • Re: [PR] Fix QueryPhraseMap.markTerminal() boost override due to conflicting query expansion [lucene] via GitHub
• [I] ToParentBlockJoinSortField does not handle missing values correctly [lucene] via GitHub
  • Re: [I] ToParentBlockJoinSortField does not handle missing values correctly [lucene] via GitHub
  • Re: [I] ToParentBlockJoinSortField does not handle missing values correctly [lucene] via GitHub
  • Re: [I] ToParentBlockJoinSortField does not handle missing values correctly [lucene] via GitHub
  • Re: [I] ToParentBlockJoinSortField does not handle missing values correctly [lucene] via GitHub
• Re: [I] switch website to new ASF logo [lucene] via GitHub
  • Re: [I] switch website to new ASF logo [lucene] via GitHub
• Re: [PR] Use Arrays.compareUnsigned in IDVersionSegmentTermsEnum and OrdsSegmentTermsEnum. [lucene] via GitHub
  • Re: [PR] Use Arrays.compareUnsigned in IDVersionSegmentTermsEnum and OrdsSegmentTermsEnum. [lucene] via GitHub
  • Re: [PR] Use Arrays.compareUnsigned in IDVersionSegmentTermsEnum and OrdsSegmentTermsEnum. [lucene] via GitHub
  • Re: [PR] Use Arrays.compareUnsigned in IDVersionSegmentTermsEnum and OrdsSegmentTermsEnum. [lucene] via GitHub
• [I] Clarifying TF-IDF / ClassicSimilarity scoring changes across Lucene versions (impact seen during Solr 5 → 8 upgrade) [lucene] via GitHub
  • Re: [I] Clarifying TF-IDF / ClassicSimilarity scoring changes across Lucene versions (impact seen during Solr 5 → 8 upgrade) [lucene] via GitHub
  • Re: [I] Clarifying TF-IDF / ClassicSimilarity scoring changes across Lucene versions (impact seen during Solr 5 → 8 upgrade) [lucene] via GitHub
  • Re: [I] Clarifying TF-IDF / ClassicSimilarity scoring changes across Lucene versions (impact seen during Solr 5 → 8 upgrade) [lucene] via GitHub
  • Re: [I] Clarifying TF-IDF / ClassicSimilarity scoring changes across Lucene versions (impact seen during Solr 5 → 8 upgrade) [lucene] via GitHub
  • Re: [I] Clarifying TF-IDF / ClassicSimilarity scoring changes across Lucene versions (impact seen during Solr 5 → 8 upgrade) [lucene] via GitHub
  • Re: [I] Clarifying TF-IDF / ClassicSimilarity scoring changes across Lucene versions (impact seen during Solr 5 → 8 upgrade) [lucene] via GitHub
  • Re: [I] Clarifying TF-IDF / ClassicSimilarity scoring changes across Lucene versions (impact seen during Solr 5 → 8 upgrade) [lucene] via GitHub
  • Re: [I] Clarifying TF-IDF / ClassicSimilarity scoring changes across Lucene versions (impact seen during Solr 5 → 8 upgrade) [lucene] via GitHub
  • Re: [I] Clarifying TF-IDF / ClassicSimilarity scoring changes across Lucene versions (impact seen during Solr 5 → 8 upgrade) [lucene] via GitHub
• [PR] Apply the alternate maven mirror via `LuceneRootConfigurationPlugin` [lucene] via GitHub
  • Re: [PR] Apply the alternate maven mirror via `LuceneRootConfigurationPlugin` [lucene] via GitHub
  • Re: [PR] Apply the alternate maven mirror via `LuceneRootConfigurationPlugin` [lucene] via GitHub
• Re: [PR] Shrink FuzzySet public API surface area [lucene] via GitHub
  • Re: [PR] Shrink FuzzySet public API surface area [lucene] via GitHub
  • Re: [PR] Shrink FuzzySet public API surface area [lucene] via GitHub
  • Re: [PR] Shrink FuzzySet public API surface area [lucene] via GitHub
• [PR] Allow AlreadyClosedException to be a possible outcome of injecting fake exceptions in TestIndexFileDeleter [lucene] via GitHub
  • Re: [PR] Allow AlreadyClosedException to be a possible outcome of injecting fake exceptions in TestIndexFileDeleter [lucene] via GitHub
• [PR] Fix the 'beast' task (regression in gradle 9+). [lucene] via GitHub
  • Re: [PR] Fix the 'beast' task (regression in gradle 9+). [lucene] via GitHub
• Re: [PR] Add a getImplementationName method to VectorizationProvider that returns the name of the selected implementation [lucene] via GitHub
• [PR] build(deps): bump basedpyright from 1.36.1 to 1.36.2 in /dev-tools/scripts [lucene] via GitHub
  • Re: [PR] build(deps): bump basedpyright from 1.36.1 to 1.36.2 in /dev-tools/scripts [lucene] via GitHub
• Re: [I] Opening of vector files with ReadAdvice.RANDOM_PRELOAD [lucene] via GitHub
  • Re: [I] Opening of vector files with ReadAdvice.RANDOM_PRELOAD [lucene] via GitHub
• Re: [PR] Add post-collection facets support to the new faceting API [lucene] via GitHub
  • Re: [PR] Add post-collection facets support to the new faceting API [lucene] via GitHub
  • Re: [PR] Add post-collection facets support to the new faceting API [lucene] via GitHub
• Re: [PR] Allow Collectors to re-order segments for non-exhaustive searches [lucene] via GitHub
  • Re: [PR] Allow Collectors to re-order segments for non-exhaustive searches [lucene] via GitHub
  • Re: [PR] Allow Collectors to re-order segments for non-exhaustive searches [lucene] via GitHub
  • Re: [PR] Allow Collectors to re-order segments for non-exhaustive searches [lucene] via GitHub
  • Re: [PR] Allow Collectors to re-order segments for non-exhaustive searches [lucene] via GitHub
  • Re: [PR] Allow Collectors to re-order segments for non-exhaustive searches [lucene] via GitHub
  • Re: [PR] Allow Collectors to re-order segments for non-exhaustive searches [lucene] via GitHub
• [PR] Use alternate maven mirror [lucene] via GitHub
  • Re: [PR] Add alternate maven mirror [lucene] via GitHub
• Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
  • Re: [PR] Use native dot product in Lucene [lucene] via GitHub
• [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
  • Re: [I] Builds on github reporting http 429 [lucene] via GitHub
• [I] Indexing "invalid" HNSW vectors does not trigger error until merge and/or CheckIndex [lucene] via GitHub
  • Re: [I] Indexing "invalid" HNSW vectors does not trigger error until merge and/or CheckIndex [lucene] via GitHub
  • Re: [I] Indexing "invalid" HNSW vectors does not trigger error until merge and/or CheckIndex [lucene] via GitHub
  • Re: [I] Indexing "invalid" HNSW vectors does not trigger error until merge and/or CheckIndex [lucene] via GitHub
  • Re: [I] Indexing "invalid" HNSW vectors does not trigger error until merge and/or CheckIndex [lucene] via GitHub
  • Re: [I] Indexing "invalid" HNSW vectors does not trigger error until merge and/or CheckIndex [lucene] via GitHub
  • Re: [I] Indexing "invalid" HNSW vectors does not trigger error until merge and/or CheckIndex [lucene] via GitHub
  • Re: [I] Indexing "invalid" HNSW vectors does not trigger error until merge and/or CheckIndex [lucene] via GitHub
• Re: [PR] build(deps): bump basedpyright from 1.34.0 to 1.36.1 in /dev-tools/scripts [lucene] via GitHub
• Re: [PR] build(deps): bump ruff from 0.14.6 to 0.14.10 in /dev-tools/scripts [lucene] via GitHub
• Re: [PR] build(deps): bump holidays from 0.85 to 0.87 in /dev-tools/scripts [lucene] via GitHub
• Re: [PR] ci: bump astral-sh/setup-uv from 7.1.4 to 7.1.6 [lucene] via GitHub
• Re: [PR] ci: bump actions/stale from 10.1.0 to 10.1.1 [lucene] via GitHub
• Re: [PR] ci: bump github/codeql-action from 3.30.5 to 4.31.9 [lucene] via GitHub
• Re: [PR] ci: bump actions/checkout from 6.0.0 to 6.0.1 [lucene] via GitHub
• Re: [PR] ci: bump actions/upload-artifact from 5.0.0 to 6.0.0 [lucene] via GitHub

• Later messages