Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Integrate Jvector engine as another vector engine of choice #2386

Open
sam-herman opened this issue Jan 14, 2025 · 0 comments
Open
Assignees

Comments

@sam-herman
Copy link

sam-herman commented Jan 14, 2025

Is your feature request related to a problem?
Currently k-NN plugin supports 3 engines, Nmslib, Faiss and Lucene.
In this change I would like to integrate JVector as another engine of choice.
There are a number of reasons to doing so:

  1. Disk ANN - JVector is capable to perform search without loading the entire index into RAM.
  2. Compatibility - JVector is compatible with Cassandra. Which allows to more easily transfer vector encoded data from Cassandra to OpenSearch and vice versa.

What solution would you like?
Introduce JVector into K-NN plugin as another supported engine.

What alternatives have you considered?
NA

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

No branches or pull requests

2 participants