semantic-kernel icon indicating copy to clipboard operation
semantic-kernel copied to clipboard

fix the serialize bug when delete a Qdrant point

Open EachShow opened this issue 2 years ago • 4 comments

Motivation and Context

fixed the bug #970

Description

Contribution Checklist

  • [x] The code builds clean without any errors or warnings
  • [x] The PR follows SK Contribution Guidelines (https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
  • [x] The code follows the .NET coding conventions (https://learn.microsoft.com/dotnet/csharp/fundamentals/coding-style/coding-conventions) verified with dotnet format
  • [x] All unit tests pass, and I have added new tests where possible
  • [x] I didn't break anyone :smile:

EachShow avatar May 18 '23 02:05 EachShow

@microsoft-github-policy-service agree

EachShow avatar May 18 '23 03:05 EachShow

This seems to be doing more than fixing bug, and it's hard to see where any bug fix is happening. The UT added doesn't do any deletion of points. It seems like it's more about adding a new method ListPoints that should likely be part of the IMemoryStore interface and deserves a full proposal.

Abstract classes can not be deserialized. "Microsoft.SemanticKernel.Connectors.Memory.Qdrant.Http.ApiSchema.QdrantResponse" is an abstract class. So the bug happened

EachShow avatar May 22 '23 02:05 EachShow

@EashShow would you mind splitting this PR in two parts, the part fixing the deserialization bug, and the other one adding a method to the IQdrantVectorDbClient interface ? Your fix would be dearly appreciated here 🙏

Poltuu avatar May 22 '23 09:05 Poltuu

@EashShow would you mind splitting this PR in two parts, the part fixing the deserialization bug, and the other one adding a method to the IQdrantVectorDbClient interface ? Your fix would be dearly appreciated here 🙏

Yes, no problem

EachShow avatar May 24 '23 05:05 EachShow

When can we expect a new version of the NuGet packages?

This is something that we are needing.

rliberoff avatar May 31 '23 11:05 rliberoff

The original bug #970 has already been fixed, and what remains here is mostly documentation and additional functionality. @EashShow closing the PR, but if you feel the other changes are valuable, please re-submit with description of added features and new tests.

shawncal avatar Jun 23 '23 16:06 shawncal