Embedding Normalization Options #8145
Open
+140
−44
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces the new API parameter
normalize
for the/api/embed
and/api/embeddings
endpoints that allow the user to explicitly enable/disable normalization. The default behavior of both endpoints is preserved (normalization forembed
, no normalization forembeddings
), but this allows them to produce equivalent output to avoid future confusion.Issues
Discussion
The
/api/embeddings
endpoint is deprecated according to the docs. An argument could be made that we should not add this functionality to this endpoint and simply document around the discrepancy. I'd be totally open to this!Testing
I updated the
embed_test.go
to include the various combinations againstembed
andembedding
. I ran them as follows: