[BUG] Lucene: keep thin-JAR SPI registrations self-owned
Open
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
Problem
The cuvs-lucene service descriptor republishes Lucene-owned vector-format providers already registered by Lucene itself, and current tests do not assert the exact contents or fresh-JVM behavior of the published thin JAR.
Proposed change
- Register only providers owned and shipped by cuvs-lucene.
- Add a post-package integration test against the actual thin JAR.
- Verify exact SPI descriptors and owned production classes.
- Exclude Lucene classes, base cuvs-java classes, dependency payloads, and test-only diagnostics.
- Resolve packaged providers in a fresh JVM without
target/classesmasking omissions.
The logical provider set remains unchanged when the declared Lucene dependency is present. Related to #2512.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the cuvs-lucene thin-JAR packaging configuration, SPI descriptors, and existing tests. Run the post-package integration path in a fresh JVM, then verify that descriptors contain only cuvs-lucene-owned production providers and exclude the named Lucene, cuvs-java, dependency, and diagnostic classes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100