Skip to content

Add SVS leanvec ood support#1666

Draft
ethanglaser wants to merge 2 commits into
zilliztech:mainfrom
ethanglaser:dev/eglaser-svs-leanvec-ood
Draft

Add SVS leanvec ood support#1666
ethanglaser wants to merge 2 commits into
zilliztech:mainfrom
ethanglaser:dev/eglaser-svs-leanvec-ood

Conversation

@ethanglaser

Copy link
Copy Markdown

Adds knowhere wrapper over SVS LeanVec OOD, which is present in FAISS

Signed-off-by: ethanglaser <ethan.glaser@intel.com>
@sre-ci-robot

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ethanglaser
To complete the pull request process, please assign marcelo-cjl after the PR has been reviewed.
You can assign the PR to them by writing /assign @marcelo-cjl in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sre-ci-robot

Copy link
Copy Markdown
Collaborator

Welcome @ethanglaser! It looks like this is your first PR to zilliztech/knowhere 🎉

@mergify

mergify Bot commented Jun 4, 2026

Copy link
Copy Markdown

@ethanglaser 🔍 Important: PR Classification Needed!

For efficient project management and a seamless review process, it's essential to classify your PR correctly. Here's how:

  1. If you're fixing a bug, label it as kind/bug.
  2. For small tweaks (less than 20 lines without altering any functionality), please use kind/improvement.
  3. Significant changes that don't modify existing functionalities should be tagged as kind/enhancement.
  4. Adjusting APIs or changing functionality? Go with kind/feature.

For any PR outside the kind/improvement category, ensure you link to the associated issue using the format: “issue: #”.

Thanks for your efforts and contribution to the community!.

@ethanglaser

Copy link
Copy Markdown
Author

On hold for benchmarking

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants