Skip to content

Creating and querying a Vector Search index

Databricks Vector Search lets you create a self-updating vector index over data stored in a Delta table, enabling similarity search for RAG and other GenAI applications. You create an index via the Vector Search UI, SDK, or API by pointing it at a source Delta table and an embedding model (or precomputed embedding column), then query it using similarity_search to retrieve the most relevant chunks/documents for a given query.

1 · Learn the must-know

  • A Vector Search endpoint must exist first (compute layer) before you can create an index on top of it.
  • There are two index types: Delta Sync Index, which automatically syncs with changes to the source Delta table, and Direct Vector Access Index, which is managed manually via API without a source table sync.
  • The source Delta table must have Change Data Feed enabled for Delta Sync indexes to track updates, inserts, and deletes.
  • You can either provide precomputed embeddings in a column or specify a Databricks-hosted embedding model endpoint so the index computes embeddings automatically from a text column.
  • Querying is done via the similarity_search API (or SDK/REST), specifying the query text or vector, number of results (num_results), and optionally metadata filters.
  • Vector Search indexes and endpoints are governed by Unity Catalog permissions, so access control follows standard UC grant/revoke on the underlying catalog/schema/table objects.

2 · Check your understanding

Check this objectiveFree · always available

A Generative AI Engineer builds a RAG app on a Databricks Vector Search index synced from a Delta table named support_tickets that receives new rows every 2 to 3 minutes. The application must reflect newly ingested tickets within about a minute, and the team cannot rely on invoking manual sync calls. Which pipeline type should the engineer configure when creating the Delta Sync index?

Your objective map0 tried · 0 answered correctly · 56 untouched

What you have tried across Databricks GenAI Engineer's objectives, not a readiness score.

Design Applications10.71% of the exam*0 of 6 tried
Data Preparation14.29% of the exam*0 of 8 tried
Application Development23.21% of the exam*0 of 13 tried
Assembling and Deploying Applications26.79% of the exam*0 of 15 tried
Governance7.14% of the exam*0 of 4 tried
Evaluation and Monitoring17.86% of the exam*0 of 10 tried

* Our estimate. Databricks publishes no section weights.

3 · Keep going