Skip to content

[MEVD] Port the Pinecone connector to use Pinecone.Client #10415

New issue
New issue
Closed
#10952
Closed
[MEVD] Port the Pinecone connector to use Pinecone.Client#10415
#10952
Assignees
adamsitnik
Labels
.NETIssue or Pull requests regarding .NET codeBuildFeatures planned for next Build conferencememorymemory connectormsft.ext.vectordataRelated to Microsoft.Extensions.VectorDatask team issueA tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)

Description

@roji
Shay Rojansky (roji)
opened on Feb 5, 2025

The current Pinecone connector uses Pinecone.NET, which is the older community-written SDK; Pinecone have since published an official, internally-developed SDK called Pinecone.Client, which is shown in official C# samples in their documentation etc.

In addition, in my attempts to set up container-based integration tests with the Pinecone local emulator, the current connector failed to work properly, whereas Pinecone.Client works well.

In other words, it looks like we'll need to port over the Pinecone connector to use the newer, official Pinecone.Local SDK.

Once that's done, also create an integration test suite like the others from #10273, and implement LINQ-based filtering.

Activity

  1. Shay Rojansky (roji)
    added
    .NETIssue or Pull requests regarding .NET code
    memory
    memory connector
    msft.ext.vectordataRelated to Microsoft.Extensions.VectorData
    on Feb 5, 2025
  2. Shay Rojansky (roji)
    self-assigned this
    on Feb 5, 2025
  3. Mark Wallace (markwallace-microsoft)
    added
    triage
    BuildFeatures planned for next Build conference
    on Feb 5, 2025
  4. Mark Wallace (markwallace-microsoft)
    added this to Semantic Kernelon Feb 6, 2025
  5. Mark Wallace (markwallace-microsoft)
    moved this to Sprint: Planned in Semantic Kernelon Feb 6, 2025
  6. Mark Wallace (markwallace-microsoft)
    moved this from Sprint: Planned to Backlog: Planned in Semantic Kernelon Feb 6, 2025
  7. Shay Rojansky (roji)
    assigned
    Adam Sitnik (adamsitnik)
    and unassigned
    Shay Rojansky (roji)
    on Feb 6, 2025
  8. Shawn Henry (sphenry)
    removed
    triage
    on Feb 6, 2025
  9. EvanChaki (evchaki)
    added
    sk team issueA tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)
    on Feb 6, 2025
  10. Mark Wallace (markwallace-microsoft)
    moved this from Backlog: Planned to Sprint: Planned in Semantic Kernelon Feb 10, 2025
  11. Shay Rojansky (roji)
    changed the title [-].Net MEVD: Port the Pinecone connector to use Pinecone.Client[/-] [+][MEVD] Port the Pinecone connector to use Pinecone.Client[/+] on Mar 11, 2025
  12. Shay Rojansky (roji)
    moved this from Sprint: Planned to Sprint: In Progress in Semantic Kernelon Mar 11, 2025
  13. github-merge-queue
    added a commit that references this issue on Mar 20, 2025

    .Net MEVD: Port the Pinecone connector to use Pinecone.Client (#10952)

    8a8b0b5
  14. Adam Sitnik (adamsitnik)
    closed this as completedin #10952on Mar 20, 2025
  15. Mark Wallace (markwallace-microsoft)
    moved this from Sprint: In Progress to Sprint: Done in Semantic Kernelon Apr 15, 2025
  16. jcruzmot-te
    added a commit that references this issue on Sep 15, 2025

    .Net MEVD: Port the Pinecone connector to use Pinecone.Client (micros…

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

Metadata

Metadata

Assignees

Labels

.NETIssue or Pull requests regarding .NET codeBuildFeatures planned for next Build conferencememorymemory connectormsft.ext.vectordataRelated to Microsoft.Extensions.VectorDatask team issueA tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions