feat(datastore): add Qdrant data store #2
Comments
|
Hey @joshua-mo-143, excellent idea, we're always looking to add support for more vector data stores! Qdrant was not in our immediate implementation roadmap but if you want to integrate it, go for it! If you have any questions, we're more than happy to help out as well! The integration should follow the same strategy as the MongoDB integration that is already part of the repo. As you mentioned, integration is pretty straightforward with you just having to implement the traits for whatever Qdrant client you want to use. If you could also include an example or two that would be perfect! In case you were wondering, the reason we're packaging the vector store integrations in separate crates is to keep the Note that we are still tweaking the Rig API and the traits mentioned above will most likely change over time. Additionally, if you find that the existing traits could be improved (e.g.: if they are not expressive enough to capture all of Qdrant's functionality) please let us know, Rig is still very early in its development and we're always looking for feedback! Happy coding! |
mateobelanger
changed the title
* feat(chain): Initial prototype for agentic chain feature * feat: Add chain error handling * feat: Add parallel ops and rename `chain` to `pipeline` * docs: Update example * feat: Add extraction pipeline op * docs: Add extraction pipeline example * feat: Add `try_parallel!` pipeline op macro * misc: Remove unused module * style: cargo fmt * test: fix typo in test * test: fix typo in test #2 * test: Fix broken lookup op test * feat: Add `Op::batch_call` and `TryOp::try_batch_call` * test: Fix tests * docs: Add more docstrings to agent pipeline ops * docs: Add pipeline module level docs * docs: improve pipeline docs * style: clippy+fmt * fix(pipelines): Type errors * fix: Missing trait import in macros * feat(pipeline): Add id and score to `lookup` op result * docs(pipelines): Add more docstrings * docs(pipelines): Update example * test(mongodb): Fix flaky test again * style: fmt * test(mongodb): fix
Hey there!
I think adding Qdrant as a possible data store would be quite beneficial for the library as they're fairly well known within the RAG community, so adding it would increase the amount of potential use cases by quite a lot.
I'm happy to implement this for you as it looks like the scope of this is quite clear (just adding a new crate and implementing relevant traits, then adding it to the list whenever you need to release), but wanted to reach out first and make sure it's OK to add.
The text was updated successfully, but these errors were encountered: