▶ Watch ↗AI Engineer World's Fair 20261:59:10
AI on Your Lakehouse: Context Comes in Shapes, Not Queries
Read the full talk →Key ideas
Scroll to read ↓A repair copilot needs more than matching passages and valid SQL. Warehouse connections, navigable documents, and link communities give it different ways to assemble the context a question requires.
- The repair history and the manual are only the beginning2:08 ↗
- A graph, an agent, and a runnable workspace7:37 ↗
- Connections: use a graph to choose the SQL21:57 ↗
- When metadata is enough—and when to import records34:26 ↗
- Table of Contents: preserve the structure documents already have43:40 ↗
- Build an outline that can stop at the right depth52:48 ↗
- Keep the vocabulary useful to the query author1:03:09 ↗
- Search the text, then restrict it to a subtree1:08:47 ↗
- Names, freshness, and references are part of retrieval quality1:14:38 ↗
- Themes: discover groups through document links1:21:43 ↗
- Community descriptions, changing data, and trust1:33:23 ↗
- From a diagnostic code to a repair recommendation1:39:19 ↗
- Find the mismatch between the library and the field1:45:31 ↗
- Theme coverage and the join the agent still performs1:52:10 ↗