Skip to content

[Tracker] Improving cuvs-lucene release robustness #2512

Description

@imotov

Java compatibility and support

  • Raise minimum JDK for full functionality from 22 to 25 (LTS)
  • Keep JDK 21 compile-time support and add a CI job that builds/runs on JDK 21
  • Clearly document the JDK support policy (compile vs. run requirements)

Lucene support

  • Support Lucene 10.2, 10.3, 10.4, 10.5 simultaneously - repurpose [FEA] Update cuvs-lucene to Lucene 10.5 #2410 and expand with:
    1. Restructure cuvs-lucene code to support different Lucene API for each supported version
    2. restructure cuvs-lucene build to publish one JAR per Lucene minor (cuvs-lucene-10.N-<ver>.jar)
    3. Compile against lowest patch version, test against highest patch version per minor
  • Define a policy for adding new Lucene minors and dropping trailing ones

libcuvs ↔ cuvs-java ↔ cuvs-lucene compatibility

API compatibility

  • Publish an API compatibility policy for cuvs-java/cuvs-lucene (no guarantee across minors, Lucene-style)

Index file format compatibility

  • Publish an index format backward-compatibility guarantee (readable through the next major of lucene)
  • Start working on a corpus of indices from older releases and test reading them or add a harness to be able to generate old indices on demand.
  • Add backward-compatibility test matrix across Lucene versions × cuvs releases

Cross-platform compatibility

  • Add explicit runtime checks + error messages for missing CUDA/insufficient VRAM when opening GPU indices
  • Document platform/portability limits of GPU index files (snapshot/restore across clusters)

Performance guarantees

Testing

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions