Skip to content

[REVIEW] Lucene upgrade to 10.4 in cuvs-lucene - #2586

Open
punAhuja wants to merge 2 commits into
NVIDIA:mainfrom
SearchScale:puneet/cuvs-lucene-upgrade104
Open

[REVIEW] Lucene upgrade to 10.4 in cuvs-lucene#2586
punAhuja wants to merge 2 commits into
NVIDIA:mainfrom
SearchScale:puneet/cuvs-lucene-upgrade104

Conversation

@punAhuja

Copy link
Copy Markdown
Contributor

Solr 11 supports lucene 10.4, so the current cuvs artefacts (which have lucene 10.2) don't work with solr due to lucene version mismatch.

  • Bump cuvs-lucene from Lucene 10.2.0 to 10.4.0.
  • Switch vector search APIs to AcceptDocs, write HNSW graphs with GroupVarInt, and delegate codecs to Lucene104Codec (float HNSW remains lucene99).
  • Update scalar/binary CPU fallbacks for the 10.4 class layout and fix LuceneProvider so 99 and 104 instances are cached separately.

@punAhuja
punAhuja requested a review from a team as a code owner September 10, 2026 18:23
@copy-pr-bot

copy-pr-bot Bot commented Sep 10, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@imotov

imotov commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Hi @punAhuja, thank you very much for your contribution.

Unfortunately, simply moving to Lucene 10.4.0 won't work for us. Some of our users will need to remain on Lucene 10.2 for the foreseeable future because of third-party dependencies, while other platforms are eager to move to 10.5.

We need a more comprehensive solution that targets multiple Lucene versions at once. Enabling support for newer versions of Lucene is very high on our priority list and we are actively working on this at the moment.

Thanks again for the patience and the effort here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants