OndatraSQL
Run Types
On this page
Values
| Run type | Trigger | Kinds |
|---|---|---|
skip | Hash unchanged, no dep changes, no @fetch | non-fetch table only |
backfill | Hash changed, first run, config changed | All |
incremental | Hash unchanged, source data may have changed | append, merge, scd2, tracked |
full | Upstream dep changed, dep metadata missing/invalid, destructive schema evolution, OR @kind: table @fetch (always re-fetches) | table |
Hash inputs
The run-type hash includes: SQL body, @kind, @unique_key, @group_key, @partitioned_by, @incremental, @incremental_initial, and SHA256 of all config/*.sql files.
What executes per run type
| Step | skip | backfill | incremental | full |
|---|---|---|---|---|
| SQL execution | no | full query | CDC-filtered (append/merge) or full query (other kinds) | full query |
| Schema evolution | no | yes | yes | yes |
| Constraints | no | yes | yes | yes |
| Audits | no | yes (transactional) | yes (transactional) | yes (transactional) |
| Materialize | no | yes | yes | yes |
| Sink | backlog only | yes | yes | yes |
| Commit metadata | no | yes | yes | yes |
Sink on skip
When a model is skipped but has @push, the runner still drains the pending state-store backlog from previous failed pushes. No new delta is generated.
Incremental kwargs
On backfill: is_backfill=True, last_value reset to @incremental_initial.
On incremental: is_backfill=False, last_value is MAX(cursor_column) from target.