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

Regarding adding new client #254

Open
mithunputhusseri opened this issue Dec 22, 2023 · 5 comments
Open

Regarding adding new client #254

mithunputhusseri opened this issue Dec 22, 2023 · 5 comments

Comments

@mithunputhusseri
Copy link

Hi Team,

While adding a new client for testing. I have followed all the steps mentioned in the page. Finally I have also made changes in the clients/init.py file. Where I have added to the entries the DB(Enum) class. However when I restart the app the changes are not reflected in the the GUI. And there is no error thrown. Is there any other steps, I have to follow.

Thanks,
Mithun

@alwayslove2013
Copy link
Collaborator

alwayslove2013 commented Dec 22, 2023

@mithunputhusseri Maybe you can try rerunning init_bench.

@alwayslove2013
Copy link
Collaborator

BTW, you need to prepare an icon_url and color for your client in vectordb_bench/frontend/const/styles.py.

DB_TO_ICON = {
DB.Milvus: "https://assets.zilliz.com/milvus_c30b0d1994.png",
DB.ZillizCloud: "https://assets.zilliz.com/zilliz_5f4cc9b050.png",
DB.ElasticCloud: "https://assets.zilliz.com/Elatic_Cloud_dad8d6a3a3.png",
DB.Pinecone: "https://assets.zilliz.com/pinecone_94d8154979.png",
DB.QdrantCloud: "https://assets.zilliz.com/qdrant_b691674fcd.png",
DB.WeaviateCloud: "https://assets.zilliz.com/weaviate_4f6f171ebe.png",
DB.PgVector: "https://assets.zilliz.com/PG_Vector_d464f2ef5f.png",
DB.PgVectoRS: "https://assets.zilliz.com/PG_Vector_d464f2ef5f.png",
DB.Redis: "https://assets.zilliz.com/Redis_Cloud_74b8bfef39.png",
DB.Chroma: "https://assets.zilliz.com/chroma_ceb3f06ed7.png",
}
# RedisCloud color: #0D6EFD
# Chroma color: #FFC107
COLOR_MAP = {
DB.Milvus.value: "#0DCAF0",
DB.ZillizCloud.value: "#0D6EFD",
DB.ElasticCloud.value: "#04D6C8",
DB.Pinecone.value: "#6610F2",
DB.QdrantCloud.value: "#D91AD9",
DB.WeaviateCloud.value: "#20C997",
DB.PgVector.value: "#4C779A",
DB.Redis.value: "#0D6EFD",
}

@mithunputhusseri
Copy link
Author

Hi Team,
I have made those changes aswell. But still the changes are not reflected. I have debugged this issue further and found out that the issue is with Streamlit framework. It uses a file cache system. Which cache file changes. It heavily depends on file watchers to read file changes and restart. However somehow this file watcher is buggy and new changes are not getting reflected. Which causes this issue.
Streamlit issue page: https://discuss.streamlit.io/t/re-run-refresh-does-not-update-page-anymore-on-1-24-0-need-restart-of-streamlit-for-update-to-happen/46356/7

This is a weird issue and if run streamlit run file.py on individual files new changes get reflected. But branched file changes are not reflected. It would be great if you could somehow turn off file cache for streamlit. Since this part of the framework is buggy and they have not been able to fix it for past several labels.

Thanks,
Mithun

@alwayslove2013
Copy link
Collaborator

@mithunputhusseri Thanks so much~ We'll keep an eye on Streamlit.

We wanna know whether your newly added client works now.

Another possibility we found during our testing is that when you have more than one vectordb-bench repo on your computer (e.g. installed one via pip install and another cloned via git), there may be a problem with the installer pointing to the wrong package so that the file changes are not tracked correctly.

If you have two vectordb-bench on your computer, go inside the dir of the right repo and the following code will resolve it to the current directory.

pip install -e ".[test]"
init_bench

@mithunputhusseri
Copy link
Author

sure @alwayslove2013 , I will try this out

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

No branches or pull requests

2 participants