Skip to content

.Net MEVD: Obsolete the legacy IMemoryStore #10808

Closed

Description

@roji

The current MEVD connectors contains both the new IVectorStore implementations and the legacy IMemoryStore implementations; the latter are legacy at this point, and users should be moving away from them to the new IVectorStore implementations.

We need to finalize the exact plan here, but we should start by obsoleting all IMemoryStore-related APIs to signal to users to move to IVectorStore; the obsoletion message would ideally point to a migration guide, a cutoff date, etc.

Activity

  1. moved this from Backlog: Planned to Sprint: In Progress in Semantic Kernelon Mar 18, 2025
  2. moved this to Sprint: In Progress in Semantic Kernelon Mar 18, 2025
  3. added a commit that references this issue on Mar 18, 2025
    c1d4709
  4. moved this from Sprint: In Progress to Sprint: In Review in Semantic Kernelon Mar 18, 2025
  5. added 2 commits that reference this issue on Mar 18, 2025
    1c4944b
    971e9db
  6. added 2 commits that reference this issue on Mar 19, 2025
    e38b31c
    e896415
  7. moved this from Sprint: In Review to Sprint: Done in Semantic Kernelon Mar 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

.NETIssue or Pull requests regarding .NET codeBuildFeatures planned for next Build conferencememorymemory connectormsft.ext.vectordataRelated to Microsoft.Extensions.VectorData

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions