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.

Sign up for GitHub

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

Jump to bottom

.Net MEVD: Port the Pinecone connector to use Pinecone.Client #10415

Open
roji opened this issue Feb 5, 2025 · 0 comments
Open

.Net MEVD: Port the Pinecone connector to use Pinecone.Client #10415

roji opened this issue Feb 5, 2025 · 0 comments
Assignees
@adamsitnik
Labels
Build Features planned for next Build conference memory connector memory msft.ext.vectordata Related to Microsoft.Extensions.VectorData .NET Issue or Pull requests regarding .NET code sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)

Comments

@roji
Copy link
Member

roji commented Feb 5, 2025 •
edited
Loading

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.
@roji roji added .NET Issue or Pull requests regarding .NET code memory memory connector msft.ext.vectordata Related to Microsoft.Extensions.VectorData labels Feb 5, 2025
@roji roji self-assigned this Feb 5, 2025
@markwallace-microsoft markwallace-microsoft added triage Build Features planned for next Build conference labels Feb 5, 2025
@markwallace-microsoft markwallace-microsoft moved this to Sprint: Planned in Semantic Kernel Feb 6, 2025
@markwallace-microsoft markwallace-microsoft moved this from Sprint: Planned to Backlog: Planned in Semantic Kernel Feb 6, 2025
@roji roji assigned adamsitnik and unassigned roji Feb 6, 2025
@sphenry sphenry removed the triage label Feb 6, 2025
@evchaki evchaki added the sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) label Feb 6, 2025
@roji roji mentioned this issue Feb 8, 2025
Open
@markwallace-microsoft markwallace-microsoft moved this from Backlog: Planned to Sprint: Planned in Semantic Kernel Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adamsitnik adamsitnik

Labels
Build Features planned for next Build conference memory connector memory msft.ext.vectordata Related to Microsoft.Extensions.VectorData .NET Issue or Pull requests regarding .NET code sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)
Projects
Semantic Kernel
Status: Sprint: Planned
Milestone
No milestone
Development

No branches or pull requests
5 participants
@roji @adamsitnik @sphenry @evchaki @markwallace-microsoft