Doris Summit 2026Day 2 · From Streaming Data to Trusted Context
Dave Stokes · DBeaver
AI assistants write fluent SQL, but they don't know your Apache Doris lakehouse. They can't tell which catalog holds the customers, which key joins the tables, or which Iceberg partition keeps a query from scanning everything. This session follows one business question through a Doris cluster that spans internal tables, Iceberg and a MySQL JDBC catalog. An engineer answers it first in DBeaver, then an AI agent tries the same task. The agent's first answer looks plausible but is wrong. We'll show what the agent needs to be taught: structure, meaning through table and column comments, and business rules captured in views. We'll also cover what it should never see and how DBeaver Community and Enterprise control what leaves your machine. Finally, we'll set guardrails in Doris itself: read-only users, workload groups and query timeouts. You'll leave with a practical checklist for letting humans and agents safely share the same data.
Developer Advocate & Community Manager · DBeaver
Dave Stokes has worked for organizations ranging alphabetically from the American Heart Association to Xerox in areas ranging from anti-submarine warfare to webmaster. He lives in a small Texas town with the required hound dog and pickup truck. Dave is the Author of MySQL & JSON - A Practical Programming Guide, now in a second edition.
LinkedIn ↗ · Dave StokesKeep exploring
From Streaming Data to Trusted Context
From Streaming Data to Trusted Context
From Streaming Data to Trusted Context
