Skip to Content
We are live but in Staging 🎉
Data EnginesVectorRecipesOverview

Recipes

Self-contained, runnable search scenarios over vector collections, grounded in real surfaces with troubleshooting tables for what actually goes wrong. These recipes are about reading — for creating collections (BYO or auto-embed), see the Pipelines recipes linked below.

What’s here

RecipeKey surfacesWhen you need it
Multi-collection SearchPOST /:bucket/search/vector (omit the collection list) · warnings[] · collectionStatuses[]Search across multiple pipeline collections in one query. Covers the compatibility group key and observability.
Hybrid + RerankPOST /:bucket/search/vector · the cross-group RRF merge at k=60What the route actually fuses, what the request fields do and don’t do, and where the verifiable evidence stops.
Multimodal Searchmultipart POST /:bucket/search/vector · visual_embedding_indexQuery by a file upload, and the content-type → modality routing rule.

Creating collections — over in Pipelines

The two collection-creation recipes moved to Pipelines, because building a collection is a control-plane / ingest concern:

Conventions used in these recipes

  • The search route has no wire clientPOST /:bucket/search/vector is control-plane HTTP, so those examples use dodil data search or curl. Raw KNN by a vector you already hold is a data-plane op (SQL / Qdrant / Pinecone / dodil data vsearch), covered in the Pipelines → External Collection recipe.
  • Endpoints: control plane https://api.data.dodil.io; data-plane doors qdrant.uk-lon-1.dodil.io, pinecone.uk-lon-1.dodil.io, table.uk-lon-1.dodil.io, pg.uk-lon-1.dodil.io:5432 — see Connect.
  • Consistent example collections: docs (a text_embedding_index pipeline collection), product-images (a visual_embedding_index pipeline collection).

See also