Skip to content

[DOC] Lucene: clarify codec behavior and Java test commands #2623

Description

@nvzm123

Problem

The cuvs-lucene README currently describes every codec as gracefully falling back to CPU, calls the GPU-search codec an HNSW build/search path, and gives ambiguous Java-test instructions. Its example command is also labeled as a test command.

Proposed change

  • Distinguish accelerated-HNSW CPU fallback from the GPU-search codec's cuVS requirement.
  • Describe CuVS2510GPUSearchCodec as CAGRA build and search.
  • Clarify that persisted accelerated codec names still require a compatible provider.
  • Document the root --run-java-tests commands, native-library prerequisite, and Surefire/Failsafe lifecycle.
  • Label the example command as an example rather than the test suite.

This is documentation-only and does not change code, APIs, defaults, artifacts, or persisted formats.

Activity

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

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