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
I'm fairly new to coding and I apologize if this isn't the right place for my question—please let me know if it should be posted elsewhere.
I'm working on developing a Q&A chatbot that leverages a respected medical database here in Sweden. I've successfully gotten the chatbot to function, but I'm facing a challenge with the database management, particularly with PDFs and their associated vector embeddings.
Here are my two main questions:
Is there a way to back up the PDF and embeddings database to Azure? Specifically, I want to ensure that if I need to run azd down followed by azd up, the system doesn't re-analyze all the previously processed PDFs. Is it possible to separate the vector/embeddings database from the main application so that it remains unaffected when I take down the whole application?
Can this type of database be downloaded locally? And if it is possible how can I upload it back to a azure resource group. This would allow me to manually integrate a previously created PDF/embeddings database into the Azure resource group whenever I use azd down.
The text was updated successfully, but these errors were encountered:
Hello everyone,
I'm fairly new to coding and I apologize if this isn't the right place for my question—please let me know if it should be posted elsewhere.
I'm working on developing a Q&A chatbot that leverages a respected medical database here in Sweden. I've successfully gotten the chatbot to function, but I'm facing a challenge with the database management, particularly with PDFs and their associated vector embeddings.
Here are my two main questions:
Can this type of database be downloaded locally? And if it is possible how can I upload it back to a azure resource group. This would allow me to manually integrate a previously created PDF/embeddings database into the Azure resource group whenever I use azd down.
The text was updated successfully, but these errors were encountered: