New Feature: Why Milvus connector not impl VectorStore?

Open
#13,391 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

  • #14577 by @Nanduu24 — closed without merging

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
csharp
Domain
databases

Research direction

Start by reading the Milvus connector and comparing its current IMemoryStore integration with the VectorStore abstraction used by the Postgres, QdrantVectorStore, and RedisVectorStore connectors. Determine whether changing the connector is intended and what compatibility or migration requirements apply. Done requires a decided scope for VectorStore support and corresponding implementation guidance or acceptance criteria.

Written by the indexing model from the issue text.

Description


name: Feature request
about: Suggest an idea for this project


The Postgres,QdrantVectorStore ,RedisVectorStore any other is impl abstrat class VectorStore.
Why Milvus connector not impl VectorStore? is IMemoryStore
Any plan change Milvus connector to impl VectorStore?

Dominant language
C#
Stars
28.8k
Forks
4.9k
Avg merge
2d 17h
Merged PRs (30d)
48

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/semantic-kernel

All issues in microsoft/semantic-kernel

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.