Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a way to pass a string as a query argument to perform vector search #384

Open
deepbuzin opened this issue Dec 7, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@deepbuzin
Copy link

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.

Screenshot 2024-12-07 at 11 19 53 AM

Current workflow:

  1. Set up some way externally (e.g. a Python script) to do the API request to transform text into an embedding
  2. 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:

  1. Once the UI detects an array<float32> parameter, it offers a choice between the normal widget and a text embedding generation widget.
  2. 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).
  3. The UI handles the API request and passes an array<float32> to the DB.
@deepbuzin deepbuzin added the enhancement New feature or request label Dec 7, 2024
@deepbuzin
Copy link
Author

@jaclarke, @1st1 also asked that you have a chat with him about this when you get around to it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants