issues  

Messages by Thread

• • Re: [I] Need QueryParser support for BooleanQuery.minNrShouldMatch [LUCENE-466] [lucene] via GitHub
  • Re: [I] Need QueryParser support for BooleanQuery.minNrShouldMatch [LUCENE-466] [lucene] via GitHub
• [I] Reading SegmentInfo and FieldInfo Map and Set fields perform unecessary sorting and object creation [lucene] via GitHub
  • Re: [I] Reading SegmentInfo and FieldInfo Map and Set fields perform unecessary sorting and object creation [lucene] via GitHub
  • Re: [I] Reading SegmentInfo and FieldInfo Map and Set fields perform unecessary sorting and object creation [lucene] via GitHub
  • Re: [I] Reading SegmentInfo and FieldInfo Map and Set fields perform unecessary sorting and object creation [lucene] via GitHub
  • Re: [I] Reading SegmentInfo and FieldInfo Map and Set fields perform unecessary sorting and object creation [lucene] via GitHub
  • Re: [I] Reading SegmentInfo and FieldInfo Map and Set fields perform unecessary sorting and object creation [lucene] via GitHub
• [I] FilterIndexInput and FilterIndexOutput override the behavior of the instance that they decorate [lucene] via GitHub
  • Re: [I] FilterIndexInput and FilterIndexOutput override the behavior of the instance that they decorate [lucene] via GitHub
  • Re: [I] FilterIndexInput and FilterIndexOutput override the behavior of the instance that they decorate [lucene] via GitHub
  • Re: [I] FilterIndexInput and FilterIndexOutput override the behavior of the instance that they decorate [lucene] via GitHub
  • Re: [I] FilterIndexInput and FilterIndexOutput override the behavior of the instance that they decorate [lucene] via GitHub
  • Re: [I] FilterIndexInput and FilterIndexOutput override the behavior of the instance that they decorate [lucene] via GitHub
  • Re: [I] FilterIndexInput and FilterIndexOutput override the behavior of the instance that they decorate [lucene] via GitHub
  • Re: [I] FilterIndexInput and FilterIndexOutput override the behavior of the instance that they decorate [lucene] via GitHub
  • Re: [I] FilterIndexInput and FilterIndexOutput override the behavior of the instance that they decorate [lucene] via GitHub
  • Re: [I] FilterIndexInput and FilterIndexOutput override the behavior of the instance that they decorate [lucene] via GitHub
  • Re: [I] FilterIndexInput and FilterIndexOutput override the behavior of the instance that they decorate [lucene] via GitHub
• [PR] fix: Typo in the error message [lucene] via GitHub
  • Re: [PR] fix: Typo in the error message [lucene] via GitHub
• [I] FilterWeight should delegate count() [lucene] via GitHub
  • Re: [I] FilterWeight should delegate count() [lucene] via GitHub
• [I] `TestBlockJoin.testScoreMode` test failure [lucene] via GitHub
  • Re: [I] `TestBlockJoin.testScoreMode` test failure [lucene] via GitHub
• [PR] Speed up slow LegacyBaseDocValuesFormatTestCase tests (fixes #1544) [lucene] via GitHub
  • Re: [PR] Speed up slow LegacyBaseDocValuesFormatTestCase tests (fixes #1544) [lucene] via GitHub
  • Re: [PR] Speed up slow LegacyBaseDocValuesFormatTestCase tests (fixes #1544) [lucene] via GitHub
  • Re: [PR] Speed up slow LegacyBaseDocValuesFormatTestCase tests (fixes #1544) [lucene] via GitHub
• [PR] minor change: code cleanup [lucene] via GitHub
  • Re: [PR] minor change: code cleanup [lucene] via GitHub
  • Re: [PR] minor change: code cleanup [lucene] via GitHub
  • Re: [PR] minor change: code cleanup [lucene] via GitHub
• [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
  • Re: [PR] Optimize `PointRangeQuery` for intra-segment concurrency with segment-level `DocIdSet` caching [lucene] via GitHub
• [PR] Backporting Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization into branch_10x [lucene] via GitHub
  • Re: [PR] Backporting Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization into branch_10x [lucene] via GitHub
• [I] BaseLucene80DocValuesFormatTestCase.testNumericFieldJumpTables is way too slow [lucene] via GitHub
  • Re: [I] BaseLucene80DocValuesFormatTestCase.testNumericFieldJumpTables is way too slow [lucene] via GitHub
  • Re: [I] BaseLucene80DocValuesFormatTestCase.testNumericFieldJumpTables is way too slow [lucene] via GitHub
  • Re: [I] BaseLucene80DocValuesFormatTestCase.testNumericFieldJumpTables is way too slow [lucene] via GitHub
• [PR] TestVectorUtilSupport increase delta for larger vector sizes [lucene] via GitHub
  • Re: [PR] TestVectorUtilSupport increase delta for larger vector sizes [lucene] via GitHub
  • Re: [PR] TestVectorUtilSupport increase delta for larger vector sizes [lucene] via GitHub
• [I] FastVectorHighlighter loses boost values in phrase expansion and nested queries [lucene] via GitHub
  • Re: [I] FastVectorHighlighter loses boost values in phrase expansion and nested queries [lucene] via GitHub
  • Re: [I] FastVectorHighlighter loses boost values in phrase expansion and nested queries [lucene] via GitHub
  • Re: [I] FastVectorHighlighter loses boost values in phrase expansion and nested queries [lucene] via GitHub
  • Re: [I] FastVectorHighlighter loses boost values in phrase expansion and nested queries [lucene] via GitHub
  • Re: [I] FastVectorHighlighter loses boost values in phrase expansion and nested queries [lucene] via GitHub
  • Re: [I] FastVectorHighlighter loses boost values in phrase expansion and nested queries [lucene] via GitHub
• [PR] Fix segment-specific TermInSetQuery rewrites thrashing caching policy [lucene] via GitHub
  • Re: [PR] Fix segment-specific TermInSetQuery rewrites thrashing caching policy [lucene] via GitHub
• [PR] De-dup raw vectors? [lucene] via GitHub
  • Re: [PR] De-dup raw vectors? [lucene] via GitHub
  • Re: [PR] De-dup raw vectors? [lucene] via GitHub
• [PR] Make MergingHnswGraphBuilder stable; fixes #15438 [lucene] via GitHub
  • Re: [PR] Make MergingHnswGraphBuilder stable; fixes #15438 [lucene] via GitHub
  • Re: [PR] Make MergingHnswGraphBuilder stable; fixes #15438 [lucene] via GitHub
  • Re: [PR] Make MergingHnswGraphBuilder stable; fixes #15438 [lucene] via GitHub
  • Re: [PR] Make MergingHnswGraphBuilder stable; fixes #15438 [lucene] via GitHub
• [I] MergingHnswGraphBuilder is unstable [lucene] via GitHub
  • Re: [I] MergingHnswGraphBuilder is unstable [lucene] via GitHub
  • Re: [I] MergingHnswGraphBuilder is unstable [lucene] via GitHub
  • Re: [I] MergingHnswGraphBuilder is unstable [lucene] via GitHub
• [PR] Fix TestIndexWriterWithThreads exceeding max file handles. [lucene] via GitHub
  • Re: [PR] Fix TestIndexWriterWithThreads exceeding max file handles. [lucene] via GitHub
  • Re: [PR] Fix TestIndexWriterWithThreads exceeding max file handles. [lucene] via GitHub
  • Re: [PR] Fix TestIndexWriterWithThreads exceeding max file handles. [lucene] via GitHub
  • Re: [PR] Fix TestIndexWriterWithThreads exceeding max file handles. [lucene] via GitHub
  • Re: [PR] Fix TestIndexWriterWithThreads exceeding max file handles. [lucene] via GitHub
  • Re: [PR] Fix TestIndexWriterWithThreads exceeding max file handles. [lucene] via GitHub
  • Re: [PR] Fix TestIndexWriterWithThreads exceeding max file handles. [lucene] via GitHub
• [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
  • 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
  • Re: [PR] Allow Collectors to re-order segments for non-exhaustive searches [lucene] via GitHub
• [PR] Fix flaky TestParentsChildrenBlockJoinQuery [lucene] via GitHub
  • Re: [PR] Fix flaky TestParentsChildrenBlockJoinQuery [lucene] via GitHub
• Re: [I] Handling concurrent search in QueryProfiler [lucene] via GitHub
• [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
  • 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] Highlighter QueryPhraseMap boost overridden due to conflicting query expansion [lucene] via GitHub
  • Re: [I] Highlighter QueryPhraseMap boost overridden due to conflicting query expansion [lucene] via GitHub
• [PR] deps(java): bump com.google.errorprone:error_prone_core from 2.43.0 to 2.44.0 [lucene] via GitHub
• [PR] Backport #14607 to branch_10x (Index open performs version check on each segment, ignores indexCreatedVersionMajor) [lucene] via GitHub
  • Re: [PR] Backport #14607 to branch_10x (Index open performs version check on each segment, ignores indexCreatedVersionMajor) [lucene] via GitHub
  • Re: [PR] Backport #14607 to branch_10x (Index open performs version check on each segment, ignores indexCreatedVersionMajor) [lucene] via GitHub
  • Re: [PR] Backport #14607 to branch_10x (Index open performs version check on each segment, ignores indexCreatedVersionMajor) [lucene] via GitHub
  • Re: [PR] Backport #14607 to branch_10x (Index open performs version check on each segment, ignores indexCreatedVersionMajor) [lucene] via GitHub
  • Re: [PR] Backport #14607 to branch_10x (Index open performs version check on each segment, ignores indexCreatedVersionMajor) [lucene] via GitHub
  • Re: [PR] Backport #14607 to branch_10x (Index open performs version check on each segment, ignores indexCreatedVersionMajor) [lucene] via GitHub
  • Re: [PR] Backport #14607 to branch_10x (Index open performs version check on each segment, ignores indexCreatedVersionMajor) [lucene] via GitHub
  • Re: [PR] Backport #14607 to branch_10x (Index open performs version check on each segment, ignores indexCreatedVersionMajor) [lucene] via GitHub
  • Re: [PR] Backport #14607 to branch_10x (Index open performs version check on each segment, ignores indexCreatedVersionMajor) [lucene] via GitHub
• [PR] BP Reordering Codec [lucene] via GitHub
  • Re: [PR] BP Reordering Codec [lucene] via GitHub
  • Re: [PR] BP Reordering Codec [lucene] via GitHub
  • Re: [PR] BP Reordering Codec [lucene] via GitHub
  • Re: [PR] BP Reordering Codec [lucene] via GitHub
  • Re: [PR] BP Reordering Codec [lucene] via GitHub
  • Re: [PR] BP Reordering Codec [lucene] via GitHub
• Re: [I] Should we add bfloat16 support for HNSW? [lucene] via GitHub
  • Re: [I] Should we add bfloat16 support for HNSW? [lucene] via GitHub
  • Re: [I] Should we add bfloat16 support for HNSW? [lucene] via GitHub
• Re: [I] Blended queries with boolean rewrite can result in inconsistent scores [LUCENE-9269] [lucene] via GitHub
• Re: [I] Make HNSW merges faster [lucene] via GitHub
• [PR] Apply HNSW merge optimizations when there are "no deleted vectors" instead of "no deleted documents"? [lucene] via GitHub
  • Re: [PR] Apply HNSW merge optimizations when there are "no deleted vectors" instead of "no deleted documents"? [lucene] via GitHub
  • Re: [PR] Apply HNSW merge optimizations when there are "no deleted vectors" instead of "no deleted documents"? [lucene] via GitHub
  • Re: [PR] Apply HNSW merge optimizations when there are "no deleted vectors" instead of "no deleted documents"? [lucene] via GitHub
  • Re: [PR] Apply HNSW merge optimizations when there are "no deleted vectors" instead of "no deleted documents"? [lucene] via GitHub
  • Re: [PR] Apply HNSW merge optimizations when there are "no deleted vectors" instead of "no deleted documents"? [lucene] via GitHub
• [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
  • Re: [PR] Adding support for passing an ExecutorService into DirectoryReader.open() to enable concurrent segment reader initialization [lucene] via GitHub
• [I] Should we rewrite/optimize the HNSW graph in 2nd pass? [lucene] via GitHub
  • Re: [I] Should we rewrite/optimize the HNSW graph in 2nd pass? [lucene] via GitHub
  • Re: [I] Should we rewrite/optimize the HNSW graph in 2nd pass? [lucene] via GitHub
  • Re: [I] Should we rewrite/optimize the HNSW graph in 2nd pass? [lucene] via GitHub
  • Re: [I] Should we rewrite/optimize the HNSW graph in 2nd pass? [lucene] via GitHub
  • Re: [I] Should we rewrite/optimize the HNSW graph in 2nd pass? [lucene] via GitHub
  • Re: [I] Should we rewrite/optimize the HNSW graph in 2nd pass? [lucene] via GitHub
  • Re: [I] Should we rewrite/optimize the HNSW graph in 2nd pass? [lucene] via GitHub
• [PR] Fix silly inefficiencies in HnswGraph.NodesIterator implementation [lucene] via GitHub
  • Re: [PR] Fix silly inefficiencies in HnswGraph.NodesIterator implementation [lucene] via GitHub
  • Re: [PR] Fix silly inefficiencies in HnswGraph.NodesIterator implementation [lucene] via GitHub
  • [PR] Fix silly inefficiencies in HnswGraph.NodesIterator implementation [lucene] via GitHub
  • Re: [PR] Fix silly inefficiencies in HnswGraph.NodesIterator implementation [lucene] via GitHub
  • Re: [PR] Fix silly inefficiencies in HnswGraph.NodesIterator implementation [lucene] via GitHub
• [I] Specialize HnswGraph.ArrayNodesIterator for dense case [lucene] via GitHub
  • Re: [I] Specialize HnswGraph.ArrayNodesIterator for dense case [lucene] via GitHub

• Earlier messages
• Later messages