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

[Enhancement]: Decouple Milvus's dependence on vector index types #34298

Open
1 task done
foxspy opened this issue Jul 1, 2024 · 1 comment
Open
1 task done

[Enhancement]: Decouple Milvus's dependence on vector index types #34298

foxspy opened this issue Jul 1, 2024 · 1 comment
Assignees
Labels
kind/enhancement Issues or changes related to enhancement

Comments

@foxspy
Copy link
Contributor

foxspy commented Jul 1, 2024

Is there an existing issue for this?

  • I have searched the existing issues

What would you like to be added?

In Milvus, some code heavily depends on the types of vector indices. This behavior is unreasonable, as Milvus does not grasp the specific differences between different indices. If there are indeed corresponding needs, the index engine (Knowhere) should provide the appropriate interfaces to fulfill them. With the increasing diversity of vector indices, this decoupling needs to be addressed as soon as possible.

Why is this needed?

No response

Anything else?

No response

@foxspy foxspy added the kind/enhancement Issues or changes related to enhancement label Jul 1, 2024
@foxspy
Copy link
Contributor Author

foxspy commented Jul 1, 2024

/assign @foxspy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Issues or changes related to enhancement
Projects
None yet
Development

No branches or pull requests

1 participant