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
It would be great if it was possible to customize the queries sent to different vector databases under additional parameters. For example, many of them (Supabase, Weaviate, Vectara, Qdrant and Singlestore) support pagination, offsetting or setting a range on the query results instead of just returning the top-k. ´This could be great for fetching several larger documents in parallel, and running them through prompts to shorten them before merging everything into a single chain, but to do so you'd need to be able to run separate queries that don't just return the top-k results.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
It would be great if it was possible to customize the queries sent to different vector databases under additional parameters. For example, many of them (Supabase, Weaviate, Vectara, Qdrant and Singlestore) support pagination, offsetting or setting a range on the query results instead of just returning the top-k. ´This could be great for fetching several larger documents in parallel, and running them through prompts to shorten them before merging everything into a single chain, but to do so you'd need to be able to run separate queries that don't just return the top-k results.
Beta Was this translation helpful? Give feedback.
All reactions