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.

Sign up for GitHub

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

Jump to bottom

Why store result in a vectorstore? #373

Open
RasmusN opened this issue Oct 10, 2023 · 0 comments
Open

Why store result in a vectorstore? #373

RasmusN opened this issue Oct 10, 2023 · 0 comments

Comments

@RasmusN
Copy link

RasmusN commented Oct 10, 2023

Why is the result from executed tasks stored in a vector store rather than a regular DB?

As far as I can see it's only used by the execution_agent to list what tasks have already been done. Why do we need an embedding index for this? Why not just index by task_id or even more simple, just keep it in memory?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RasmusN