-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
RAG Example for using REST API in 2.0 #5991
Comments
To start, we can simplify the scope of this activity. I will try to put myself in the shoes of a user who has tried Haystack and wants to start building a real application with it. The output of this initial activity can consist of:
|
Would be useful. I just made this app and its services. If it's any help, here's how my stack looks like
I may not be able to create a complete example, but if there's a wip, I can contribute to it. |
TO DO:
|
Closing as we agreed it's not going to be docs, to be decided whether it's an article or a tutorial. Comprehensive docs about how to deploy pipelines will follow in 2.0 |
Is your feature request related to a problem? Please describe.
We want an example of a RAG pipeline + file upload through our REST API.
Making the the app work async (async pipeline + fastAPI) would be the cherry on top of our juicy haystack 2.0 cake.
Since we need updated docker images for starting the REST API, this issue is related to #5990
Describe the solution you'd like
Ideally, we use the existing REST API and just create documentation around it.
See how the indexing pipeline is used we might need a few parameter changes.
Also, the pipeline usage in our search endpoint seems reasonably generic.
The text was updated successfully, but these errors were encountered: