-
Notifications
You must be signed in to change notification settings - Fork 266
v1.16: Multimodal search #3312
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
base: v1.16
Are you sure you want to change the base?
v1.16: Multimodal search #3312
Conversation
…/documentation into v1.16-3298-multimodal-search
…/documentation into v1.16-3298-multimodal-search
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.
It looks like the PR additionally makes changes related to code samples but unrelated to multimodal per se.
I didn't review these changes, only the multimodal ones.
The documentation looks right, I wonder if we should plan a more principled guide on how to setup a multimodal embedder with Voyage as backend 🤔
Co-authored-by: Louis Dureuil <[email protected]>
I should have mentioned that you needed not mind the code sample changes. They're a kink we haven't been able to iron out yet in our Mintlify workflow. Apologies for that, but, yes, I expected you to ignore them. Regarding the guide, yes, that is something I think is necessary, but with everything happening internally I wasn't able to make the time for it before the release. 😢 |
Since we have an existing Voyage AI guide, maybe a quick win would be adding a "Multi-modal embeddings" section there? It could simply pull from the release notes example implementation? |
Fixes #3298