Databricks’ Agent Orchestrator 🕹️, Ecosystems Beat Models 🔁, LinkedIn’s Search Brain 🔍

Open the original

Short summary

This issue covers the latest in data tooling and AI agents—from Databricks’ Agent Orchestrator and Spotify’s Vedder assistant to Feldera’s incremental view engine and LinkedIn’s MUSE semantic search. It also dives into managing agentic AI costs, building stable model ecosystems, and new open-source releases like Omnigent and Apache DataFusion 54.0.0.

  • Spotify's Vedder only kept 12.5% of automatically mined query pairs after expert review, relying on human-curated clusters over the other 70,000-dataset schema-only retrieval
  • Uber's 5,000 engineers burned through the annual AI budget by mid-April using Claude Code, showing token pricing becomes a task-economics problem once retries, orchestration, and governance overhead are counted
  • DataFusion 54.0.0 added LATERAL joins, SQL lambdas, and spill-to-disk nested loops, pushing join speeds up to 50x faster in some cases
  • Databricks' Omnigent unifies Claude Code, Codex, Pi, and in-house agents under one harness with shared security, cost limits, and session sharing

Full summary

Spotify’s Vedder puts domain experts at the center of its data assistant. Instead of relying on schema-only retrieval, Spotify divided its 70,000 datasets into 177 clusters. Experts curate each cluster with vetted question-to-SQL pairs and relevant business documents. Only 12.5 percent of automatically mined query pairs passed expert review, so Vedder uses health scores—tracking drift, validity, coverage and reproducibility—to keep its context accurate for 2,100 users. Feldera treats streaming data as incremental SQL views, using DBSP to push only row-level deltas through joins and aggregations. Inserts, updates and deletes map to Z-set changes, cutting CPU use and memory pressure compared with full recomputations. At LinkedIn, MUSE powers semantic search in the Hiring Assistant. A dual-tower embedding model learns from millions of examples labeled by an LLM teacher tied to product policy. Embedding-based retrieval narrows candidates; a downstream ranker then optimizes for engagement. AI coding agents are speeding up routine work but they can balloon technical debt if left unchecked. Teams at Uber burned through their annual AI budget by mid-April after 5,000 engineers adopted Claude Code. Hidden costs—from redundant context sent in retries, orchestration overhead and governance checks—turned token pricing into a task-economics problem. Experts now measure value per task, clamp context size and build stateful agent infrastructure to contain spending. On the tooling side, Databricks’ Omnigent meta-harness stitches together Claude Code, Codex, Pi and in-house agents under one layer, adding security, cost limits and live session sharing. Apache DataFusion 54.0.0 rolled out LATERAL joins, SQL lambdas for arrays, an Arrow-based Avro reader and spill-to-disk for nested loops, boosting join speeds by up to 50× in some cases. MotherDuck’s Flights feature lets agents launch Python-based ingestion and transformation jobs with built-in logging and versioning. The Linux Foundation’s OpenSharing project extends Delta Sharing into a standard API for models, skills and unstructured data across clouds. Meanwhile, Databricks warns that ai_parse_document pipelines can rack up LLM costs and duplicate work; adding checkpoints, versioned prompts and dedup filters—or switching to deterministic parsers when templates are stable—keeps costs and reprocessing in check.

Ask about this article