Skip to content

Conversation

@schauder
Copy link

Embedding models, that didn't have support for a MetadataModel got an additional constructor with MetadataModel as the second argument. I did not include it in all the other constructors since this would break code.

AzureOpenAiEmbeddingModel had special handling for empty results, that got lost in the change. Not sure if that is ok.

TransformersEmbeddingModel has as default, which differs from the others. Should that be changed to , which seems the most reasonable default to me and is used in the other models?

Closes #2579

Embedding models, that didn't have support for a MetadataModel got an additional constructor with MetadataModel as the second argument.
I did not include it in all the other constructors since this would break code.

AzureOpenAiEmbeddingModel had special handling for empty results, that got lost in the change.
Not sure if that is ok.

TransformersEmbeddingModel has  as default, which differs from the others. Should that be changed to , which seems the most reasonable default to me and is used in the other models?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Handling of meta data is inconsistent between different embedding models.

2 participants