-
Notifications
You must be signed in to change notification settings - Fork 1.2k
chore(cleanup)!: kill vector_db references as far as possible #3864
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
Conversation
from llama_stack_client import Agent, AgentEventLogger, RAGDocument, LlamaStackClient | ||
|
||
vector_db_id = "my_demo_vector_db" | ||
vector_store_id = "my_demo_vector_store" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this demo script needs updating -- we should not be using rag_tool cc @ehhuang ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I posted a similar one, can update later
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
draft here: #3870
has some other changes in it too.
Probably will break UI but I can fix that later as we haven't deployed it to NPM or anything so it's not a big deal |
shields Manage safety shield services. | ||
toolgroups Manage available tool groups. | ||
vector_dbs Manage vector databases. | ||
vector_stores Manage vector databases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: Manage vector stores
f622211
to
016388b
Compare
Yeah almost certainly will break the UI. |
There should not be "vector db" anywhere.