Originally created by @Jbollenbacher on GitHub (Feb 22, 2024).
I'd like to suggest using haystack as the backend for the RAG system. It's quickly becoming the industry standard and is well maintained. I figured now would be a good time to suggest it while the RAG system is still mostly in beta.
Haystack solves a lot of the basic problems like providing flexibility for swapping out embedding models and chunking strategies. It's also robust and comes with a lot of good default options. Basically it offloads the task of engineering a SOTA RAG system to another group of open source developers.
Originally created by @Jbollenbacher on GitHub (Feb 22, 2024).
I'd like to suggest using [haystack](https://github.com/deepset-ai/haystack) as the backend for the RAG system. It's quickly becoming the industry standard and is well maintained. I figured now would be a good time to suggest it while the RAG system is still mostly in beta.
Haystack solves a lot of the basic problems like providing flexibility for swapping out embedding models and chunking strategies. It's also robust and comes with a lot of good default options. Basically it offloads the task of engineering a SOTA RAG system to another group of open source developers.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Jbollenbacher on GitHub (Feb 22, 2024).
I'd like to suggest using haystack as the backend for the RAG system. It's quickly becoming the industry standard and is well maintained. I figured now would be a good time to suggest it while the RAG system is still mostly in beta.
Haystack solves a lot of the basic problems like providing flexibility for swapping out embedding models and chunking strategies. It's also robust and comes with a lot of good default options. Basically it offloads the task of engineering a SOTA RAG system to another group of open source developers.
@tjbck commented on GitHub (Mar 28, 2024):
Merging this issue with open-webui/pipelines#15, let's continue our discussion there!