-
Notifications
You must be signed in to change notification settings - Fork 5
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
Multiplexer article #297
Multiplexer article #297
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
||
If you've ever build a Haystack pipeline with more than 3-4 components, you probably noticed an annoying problem: the number of inputs to pass to the `run()` method of the pipeline seems to grow endlessly. New components take some of their input from the other components of a pipeline, but many of them also require additional input from the user. As a result, the dictionary input of `pipeline.run()` grows and grows until it becomes very repetitive. | ||
|
||
One common example of this problem is **hybrid search pipelines**, like this one: |
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.
We have a tutorial covering the hybrid retrieval (the same pipeline until PromptBuilder). Do you think that we can remove the RAG part of this pipeline to make the pipeline shorter? This way, we can still showcase a clear use case of Multiplexer, and the pipeline itself and its image would look more concise. Plus, we can link to the hybrid retrieval tutorial deepset-ai/haystack-tutorials#282
Co-authored-by: Bilge Yücel <bilgeyucel96@gmail.com>
Co-authored-by: Bilge Yücel <bilgeyucel96@gmail.com>
Co-authored-by: Bilge Yücel <bilgeyucel96@gmail.com>
Co-authored-by: Bilge Yücel <bilgeyucel96@gmail.com>
Co-authored-by: Bilge Yücel <bilgeyucel96@gmail.com>
Co-authored-by: Bilge Yücel <bilgeyucel96@gmail.com>
No description provided.