Lucene: Define and implement parameter boundaries
Nobody has claimed this yet.
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
We expose the following parameters via our cuvs-lucene API.
Build Index
- CAGRA:
- cuVS writer threads
- CAGRA Intermediate graph degree
- CAGRA Graph degree
Searching
- CAGRA ItopK
- CAGRA Search width
We need to have a valid boundary defined for each of the above parameters, and at least have basic checks in place at the cuvs-lucene level, so that only valid parameters are eventually passed to the lower-level cuVS API via the cuvs-Java layer.
Ideally, I want this defined and checks in place before we let customers use the API.
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 in the cuvs-lucene API parameter handling and trace how values reach the lower-level cuVS API through the cuvs-Java layer. Define valid boundaries and add basic checks for the listed writer-thread, CAGRA degree, ItopK, and search-width parameters; done means invalid values are rejected before being passed onward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100