8. Source Run and Lineage
8.1 What Is Source Run
When your query references cached results from other tabs, those upstream tabs may not have run yet or their data may be stale. Source Run automatically:
- Analyzes your SQL to find all dependent upstream tabs.
- Runs each upstream tab in the correct dependency order.
- Runs your target tab last.
This ensures you always query against up-to-date data.
8.2 Run Source Run and Watch Live Progress
- Open an SQL tab (Persist or Temp; the tab must contain a single SQL statement).
- Click Source Run in the toolbar.
- A progress window opens with a flow diagram:
- Each node is a tab or data source.
- Node status updates live (waiting → running → complete / error).
- You can see execution time and error messages per node.
8.3 Abort Execution
While Source Run is in progress, click Abort anytime. Completed steps are unaffected; the step currently running is cancelled.
8.4 View Lineage Graph
You can view the lineage graph without running Source Run:
- Click Check Lineage in the SQL tab toolbar (Persist and Temp tabs).
- Or choose Check Lineage on a cache item under Data → Cached.
The lineage graph visualizes the dependency chain; you can zoom and pan to explore.
8.5 Node Types
Lineage nodes can be:
| Node type | Description |
|---|---|
| Physical | Physical data files (CSV, Excel sheets, etc.) |
| Cached | Cached results from other tabs |
| Target | The target tab you are viewing |
| Unknown | Unrecognized data source |
Note: Source Run and lineage use SQL in the editor (including unsaved changes). Persist tabs materialize cache; Temp tabs can be rerun at the end and used for lineage but do not produce cache. Each tab must contain a single SQL statement.
[Image] Lineage graph showing dependencies between nodes
[Image] Source Run progress window with live node status
Design note: Source Run DAG and lineage design are in Unified Query Layer §7.2–7.3.