'JsonNumberHandlingAttribute' is only valid on a number or a collection of numbers when applied to a property or field.

Describe the bug ‘JsonNumberHandlingAttribute’ is only valid on a number or a collection of numbers when applied to a property or field.

To Reproduce Steps to reproduce the behavior: 1.QdrantVectorDbClient.cs Line-132

public async Task<QdrantVectorRecord?> GetVectorByPayloadIdAsync(...)
{
       ... 
       // Line-132
       var data = JsonSerializer.Deserialize<SearchVectorsResponse>(responseContent);
       ...
}

Expected behavior ‘JsonNumberHandlingAttribute’ is only valid on a number or a collection of numbers when applied to a property or field. See member ‘Id’ on type ‘Microsoft.SemanticKernel.Connectors.Memory.Qdrant.Http.ApiSchema.SearchVectorsResponse+ScoredPoint’.

Screenshots If applicable, add screenshots to help explain your problem.

[SOE-YoungS]

This issue seems to still be occurring in “0.15.230531.5-preview”. I’ve just updated to the latest release & with no other code changes, have just run into this issue.

Id was previously set using strings in our vector db.

IE: We’re looping though a JSON list of QnA items and saving them into a collection. The filename in our case, is named to represent the team / process the QnA list targets.

await _memory.SaveInformationAsync("QnACollection", qnaItem, $"{file.Name}-q{i}");

Not sure if we need to change anything here, but my understanding of QDrant is that a string value or an int should be accepted.

[craigomatic]

Sorry about this, we brought in a PR last week that was supposed to allow both numbers and strings for that property (Qdrant allows this) and it appears to have caused a regression.

To unblock yourself, you can remove the JsonNumberHandling attribute from ScoredPoint:

We will take another pass at fixing this!