Skip to content
All topics

Databricks AI Search

Recent items mentioning Databricks AI Search across the Databricks ecosystem — releases, news, videos, and community Q&A. Updated hourly.

60 recent items19 releases11 news12 videos18 community threads
What's happening in Databricks AI SearchAI synthesis · updated 5h ago

AI Search now natively indexes Streaming Tables, Materialized Views, and Iceberg v3+ managed tables alongside Delta, with no separate sync pipelines needed 3. The new NEAREST BY SQL join runs exact or approximate batch vector search directly on liquid-clustered Delta tables through a fused Photon operator, with no external vector store to manage 9, and it now has a Bricktalk recording 1. SDKs in Python, Java, and Go now include start and stop methods for vector search endpoints, plus new STARTING, STOPPING, and STOPPED statuses 652.

Generated daily from the 10 most recent items mentioning Databricks AI Search. Click any [N] to jump to the source.

Databricks CommunityBrickTalks TV

Bricktalk Recording | Vector Search in the Lakehouse with NEAREST BY

00today
Reddit

Databricks-managed Vector Search Index is frustrating

We are a small team, and we had to share frustration with the confusing limitations of Databricks-managed solutions, specifically Databricks-managed vector search, today. Anyone else having similar issues? Product Review on Databricks-Managed Vector Search Index The overall product intent is helpful because simplifying the process of embedding vectors and exposing the index through an endpoint drastically speeds up the time from design to production. However, the lack of expected features makes it undesirable for even small teams. Major limitations The ability to turn on the writeback table is only at the time of first index creation. Once the embedding is created, there is no way to "recover" the raw embeddings without recreating the index with the writeback option. The embeddings in the writeback table cannot be used for creating an index again. When we ran into issues of failed index creation after successful embeddings and writeback table, our only option became using those embeddings in the writeback table for self-managed index or paying a huge embedding cost to re-create the entire index. Knowledge assistants are only available for Databricks-managed index, while it cannot reap the benefits through ensuring the hybrid search (ANN + BM25) method or use filter arguments. Conclusion The critical limitations of Databricks-managed Vector Search Index, especially features that seem to allude to the use of self-managed solutions instead of enhancing themselves make it confusing what Databricks is trying to promote through these built-in features. As a small team, we expected us to be a good target audience of Databricks-managed solutions, but heavy limitations are pushing us to custom, self-managed solutions. It is unclear what target audience is for the Databricks built-in features are for, especially for the Databricks-managed Vector Search Index. submitted by /u/emeraldduck2025 [link] [comments]

00emeraldduck20252w ago
Databricks CommunityAnnouncements

Community Bricktalk | SQL-Native Vector Search

002w ago
Databricks CommunityLakebase Articles

Announcement | Lakebase Search: State-of-the-art full-text and vector search for Postgres

003w ago
Databricks CommunityGenerative AI

Knowledge Assistant fails to load after indexing; generated AI Search index cannot be reused

001mo ago
Reddit

Workshop, Sep 19: build explainable AI apps with Neo4j, GraphRAG, Cypher and LLM Agents

There's a hands-on workshop on September 19 relevant if your team runs its data platform on Databricks and is looking at adding an explainable, graph-backed RAG layer on top for reasoning over structured and unstructured data. You build: A knowledge graph in Neo4j that becomes your single source of truth for an agentic RAG system Agentic retrieval combining vector search, keyword search, and graph navigation Multi-step, verified entity and relationship extraction Text-to-Cypher for natural language graph querying Explainable, source-traceable answers with evaluation built in Runs on real financial filings and news data, working through a complete production use case. Led by Dr. Alessandro Negro, Chief Scientist at GraphAware, bestselling author. Link if you want to check it out submitted by /u/camerongreen95 [link] [comments]

00camerongreen951mo ago
Reddit

Could a “Data → Agent” composer be useful for Databricks?

I've been thinking about a gap between Databricks data and agent frameworks. Databricks already has a lot of the building blocks: - Unity Catalog - Genie / Genie Agents - MCP - Vector Search - AI Gateway - Agent skills/tools - MLflow - Omnigent / Kasal And tools like Omnigent and Kasal already solve a lot of the agent orchestration/execution side. But I'm wondering about the step before that: What if a customer already has a large, curated and governed Databricks data estate — how do we turn that data estate into an agent-ready configuration without manually wiring everything together? Something like: Existing Databricks Data Estate ↓ Data-to-Agent Composer ↓ ┌────────┼─────────┐ ↓ ↓ ↓ Domains Semantics Metrics ↓ ↓ ↓ Genie MCP Skills └────────┼─────────┘ ↓ Agent Configuration ↓ Omnigent / Kasal ↓ Agent The idea wouldn't be to build another chatbot or another agent framework. It would be a Databricks-native composition/bootstrapping layer that understands an existing Unity Catalog/data estate and generates the pieces needed for agents to work with that data — domain boundaries, semantic context, approved tools, Genie configuration, MCP exposure, skills, policies, evaluation setup, etc. In other words: Kasal/Omnigent: Agent → Tools/Data Proposed layer: Data Estate → Agent I'm curious if this is already solved somewhere in the Databricks ecosystem, or if people are currently doing this manually when building enterprise data agents. Would love to hear how others are approaching the “existing data estate → production-ready data agent” problem. submitted by /u/imsuryya [link] [comments]

00imsuryya1mo ago
Reddit

Azure AI Foundry + Databricks Architecture | Deploy Genie Agent with DAB...

Azure AI Foundry Databricks architecture, Deploy Genie Agent with DABs, Databricks Genie Agent, Azure Databricks Genie Space, how to deploy genie agent with declarative automation bundles, azure ai foundry + databricks integration, fully operating genie architecture databricks, databricks unity catalog genie agent, azure databricks bronze silver gold architecture, agent to agent nlq databricks, databricks spark python sql delta lake unity catalog, production ready genie agent deployment, databricks vector search index genie, microsoft purview databricks governance submitted by /u/macxima [link] [comments]

00macxima1mo ago
Databricks CommunityCommunity Articles

Demystifying Databricks Full Text Search: It’s Not Vector Search (And That’s Okay!)

002mo ago
Databricks CommunityGenerative AI

Building an Enterprise RAG Chatbot with Databricks Mosaic AI and Vector Search

003mo ago
Databricks CommunityGenerative AI

Governance for vector search across multi domain unstructured data

003mo ago
Databricks CommunityTechnical Blog

Sharing Vector Search Indexes Across Databricks Workspaces with Terraform

003mo ago
Databricks CommunityMVP Articles

Databricks AI Search

004mo ago
Databricks CommunityLakebase Articles

HealthCare Prior Authorizations with Databricks Lakebase Vector Search

004mo ago
RedditNews

New Databricks Certificate Announcement

Databricks has officially launched a brand-new **Databricks Context Engineer Associate** currently available in **Beta** This exam focuses on designing and managing the context layer for AI agents, including: • Prompt & instruction engineering • Retrieval systems & Vector Search • Agent memory architectures • Tool integration using MCP • Governance, PII handling & policy enforcement • Multi-agent workflows and context optimization A very interesting move as Context Engineering becomes a critical skill in building reliable enterprise AI systems. The beta exam will be delivered live at DAIS 2026.

30Few-Engineering-41355mo ago
RedditTutorial

Document Intelligence on Databricks

80% of enterprise data is locked inside PDFs, scans, emails and contracts and most teams still treat it as someone else's problem. Document Intelligence on Databricks changes that. One SQL function (ai\_parse\_document), governed by Unity Catalog, integrated with Lakeflow for ingestion, Agent Bricks for structured extraction, and Vector Search for RAG. No stitched-together OCR vendors, no brittle Python glue, no separate platform to govern. I put together with [Archika Dogra](https://www.linkedin.com/in/archikadogra/) a walkthrough showing how it actually works end-to-end from a folder of raw PDFs to queryable Delta tables and downstream agents. ▶️ [https://youtu.be/sdG73gI143c](https://youtu.be/sdG73gI143c) Curious to hear what use cases you're tackling invoices, contracts, claims, technical docs? Drop them in the comments.

82Youssef_Mrini5mo ago
RedditGeneral

Context Engineer Associate Beta Ex︁am + free attempt at DAIS

Context engineering is quickly becoming one of the key skills for building reliable AI agent systems. Databricks has just introduced the **Databricks Context Engineer Associate** **Ex︁am**, focused on designing, assembling, and governing the information AI agents receive at inference time - including prompts, retrieval systems, memory, tools, governance, and evaluation. The ex︁am is currently available as a **live beta at Data + AI Summit 2026**, and Databricks states that **one free onsite exam attempt will be offered during Summit**. Walk-ins only, one per attendee. Great opportunity for anyone working with GenAI, AI agents, Vector Search, Unity Catalog, MLflow, MCP, or Lakebase. [https://www.databricks.com/learn/certification/context-engineer-associate](https://www.databricks.com/learn/certification/context-engineer-associate)

76szymon_dybczak5mo ago
RedditHelp

Knowledge bases in medallion architecture

Would you put knowledge bases in the bronze/silver/gold layer? The raw documents definitely reside in the bronze layer. But if I create AI Agents atop a volume storing the raw documents, then the knowledge base remains in bronze. However, if I create vector embeddings/do chunking/create a vector search index, then these tables should be in the silver layer. Am I on the right track?

28RazzmatazzLiving13235mo ago