You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of working on queries that involve ext::aicapabilities a user would need to pass text embeddings as query parameters. A text embedding is a numeric representation of text that enables us to semantically compare different pieces of text using math.
Embeddings are obtained by passing text to an API like this. They are then passed into a query as an array<float32>. It is ~2000 elements long, however, which makes it difficult to input using existing UI widgets.
Current workflow:
Set up some way externally (e.g. a Python script) to do the API request to transform text into an embedding
Copy the embedding, paste it as a string parameter, then parse that in the query into array<float32>...? Haven't tried that personally, not sure if that'd work.
Desired workflow:
Once the UI detects an array<float32> parameter, it offers a choice between the normal widget and a text embedding generation widget.
When selecting the second one, the user can pass their text string as an input. They can also pick which of the configured embedding models to use (if multiple are configured in the AI tab).
The UI handles the API request and passes an array<float32> to the DB.
The text was updated successfully, but these errors were encountered:
As part of working on queries that involve
ext::ai
capabilities a user would need to pass text embeddings as query parameters. A text embedding is a numeric representation of text that enables us to semantically compare different pieces of text using math.Embeddings are obtained by passing text to an API like this. They are then passed into a query as an
array<float32>
. It is ~2000 elements long, however, which makes it difficult to input using existing UI widgets.Current workflow:
array<float32>
...? Haven't tried that personally, not sure if that'd work.Desired workflow:
array<float32>
parameter, it offers a choice between the normal widget and a text embedding generation widget.array<float32>
to the DB.The text was updated successfully, but these errors were encountered: