.Net: Bug: Some vector DBs return scores that do not match the definition of the distance function

[westey-m]

Describe the bug
For the purposes of this bug description the following vectors have been used:
[1, 0, 0, 0]
[-1, 0, 0, 0]

Examples:

DB	DistanceFunction	IdenticalActual	IdenticalExpected	OppositeActual	OppositeExpected
AzureAISearch	CosineSimilarity	1	1	0.3333334	-1
AzureAISearch	DotProductSimilarity	1	1	0.2	-1
AzureAISearch	EuclideanDistance	1	0	0.05882353	2
Pinecone	EuclideanDistance	0	0	4	2
Redis	DotProductSimilarity	0	1	2	-1
Redis	EuclideanDistance	0	0	4	2
Weaviate	DotProductSimilarity	-1	1	1	-1

We should test all distance functions for all connectors to ensure that they return the expected values.

To Reproduce

Create a redis vector store collection using DotProductSimilarity. Add a record with the following vector [1, 0, 0, 0] and do a vector search using the same vector. The score returned is -1.

Expected behavior
The score returned is 1.

Platform

• Language: C#