dbt-hodor 0.1.0__tar.gz

dbt_hodor-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 The dbt-hodor Authors
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

dbt_hodor-0.1.0/NOTICE

@@ -0,0 +1,16 @@
+dbt-hodor
+Copyright 2026 The dbt-hodor Authors
+
+This product includes software derived from dbt-state
+(https://github.com/dbt-labs/dbt-state, commit b0f3030),
+Copyright 2026 Fivetran, Inc., licensed under the Apache License, Version 2.0.
+
+Files derived from dbt-state, each modified for dbt-hodor:
+- src/dbt_hodor/state_config.py (from clients/dbt_state/src/dbt_state/plugin.py):
+  the `state:` config merge, the only upstream-derived logic in dbt-hodor
+- src/dbt_hodor/plugin.py (from clients/dbt_state/src/dbt_state/plugin.py):
+  the plugin entry point
+- src/dbt_hodor/patches.py (from clients/dbt_state/src/dbt_state/runner.py)
+
+dbt is a trademark of dbt Labs, Inc. dbt-hodor is not affiliated with or
+endorsed by dbt Labs, Inc. or Fivetran, Inc.

dbt_hodor-0.1.0/PKG-INFO

@@ -0,0 +1,209 @@
+Metadata-Version: 2.4
+Name: dbt-hodor
+Version: 0.1.0
+Summary: Reuse unchanged dbt nodes and rebuild only when code or upstream data changed. A free, self-hosted alternative to dbt State.
+Author: Isa Inalcik
+License-Expression: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Classifier: Programming Language :: Python :: 3
+Classifier: Operating System :: OS Independent
+Requires-Dist: dbt-core>=1.12,<1.13
+Requires-Dist: sqlglot>=30.22,<31
+Requires-Dist: duckdb>=1.0 ; extra == 'duckdb'
+Requires-Dist: psycopg[binary]>=3.2 ; extra == 'lakebase'
+Requires-Dist: databricks-sdk>=0.81 ; extra == 'lakebase'
+Requires-Dist: psycopg[binary]>=3.2 ; extra == 'postgres'
+Requires-Python: >=3.10
+Provides-Extra: duckdb
+Provides-Extra: lakebase
+Provides-Extra: postgres
+Description-Content-Type: text/markdown
+
+<!-- markdownlint-disable MD033 MD041 -->
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="docs/assets/hodor-logo.svg">
+    <img src="docs/assets/hodor-logo-light.svg" width="420" alt="dbt-hodor: Hold Old Data, Or Rebuild">
+  </picture>
+</p>
+
+<h1 align="center">dbt-hodor</h1>
+
+<p align="center">
+  <a href="https://github.com/alaturqua/dbt-hodor/actions/workflows/ci.yml"><img src="https://github.com/alaturqua/dbt-hodor/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
+  <img src="https://img.shields.io/badge/python-3.10%20to%203.12-blue" alt="Python 3.10 to 3.12">
+  <img src="https://img.shields.io/badge/dbt--core-1.12-orange" alt="dbt-core 1.12">
+  <img src="https://img.shields.io/badge/license-Apache--2.0-green" alt="Apache-2.0">
+  <a href="https://alaturqua.github.io/dbt-hodor/"><img src="https://img.shields.io/badge/docs-online-informational" alt="Documentation"></a>
+</p>
+
+**[Documentation](https://alaturqua.github.io/dbt-hodor/)** | **[Interactive guide](https://alaturqua.github.io/dbt-hodor/guide/)** with a run simulator | **[Design spec](https://alaturqua.github.io/dbt-hodor/design/)**
+
+dbt-hodor is a free, self-hosted alternative to dbt Labs' [dbt State](https://docs.getdbt.com/docs/deploy/dbt-state-about). It runs inside dbt. For every selected node it decides whether to reuse the object that is already in the warehouse or to build it again. A node is reused when its logic has not changed and its upstream data has not changed since the last build.
+
+It needs no dbt platform account and sends nothing to external services. State lives in a Delta table on Databricks, in a Postgres database such as Databricks Lakebase, or in a local DuckDB file.
+
+> **Status: early development.** hodor runs inside dbt and passes end-to-end tests on dbt-duckdb. Tested live on a Databricks Unity Catalog workspace with a SQL warehouse and dbt-databricks 1.12.7 (2026-10-20 and 2026-10-21): reuse of tables, incremental models (including `replace_where`), views, seeds and snapshots, replayed tests, maintenance commits (OPTIMIZE, zero-row writes, SET TBLPROPERTIES) that keep nodes reused, and real new data or a changed seed file that rebuilds them. The live test runs twice, with `use_materialization_v2` off and on, and also covers contracts with a primary key, a row filter, column masks, date-window and stamp models, and a table swapped in by `use_safer_relation_operations`. The same live suite passes on a second, independent Databricks workspace (2026-10-21). The `postgres` store is tested end to end against Databricks Lakebase. It has not run in a large production project yet. Start in shadow mode.
+
+## Why "hodor"
+
+The name is a backronym: **H**old **O**ld **D**ata, **O**r **R**ebuild. That is the only decision hodor makes, once per node.
+
+hodor holds the door in front of your warehouse. A node gets through to a rebuild only when its code changed or new data arrived upstream. Everything else keeps the data it already has.
+
+## How it works
+
+For each node in `dbt run`, `dbt build`, `dbt test`, `dbt seed` or `dbt snapshot`, hodor:
+
+1. **Hashes the logic.** For a seed this is the CSV file. Otherwise the compiled SQL is normalized with [sqlglot](https://github.com/tobymao/sqlglot) (Databricks dialect), so case, quoting, comments and table aliases do not count as changes. Values that differ on every run, such as `invocation_id`, are replaced first. The node config is hashed as well.
+2. **Checks the upstream data.** Each upstream table has a data version. On Databricks it comes from the Delta commit history; maintenance commits such as `OPTIMIZE` or `VACUUM` do not count as data changes. On DuckDB it is a content fingerprint.
+3. **Decides.** It compares both against the record of the node's last build and returns `reuse` or `build`, with a reason code.
+4. **Records.** It appends one record per node to the state table.
+
+A run with no code changes skips sqlglot entirely: when the compiled SQL is byte-identical to the last build, hodor reuses the stored analysis. For 10,000 compiled models, hashing then takes about 0.1 seconds instead of about 4 minutes.
+
+### Safety: fail open
+
+Every failure leads to a build, never to a reuse. An error while deciding, a store that cannot be read, a table whose data version is unknown, an input hodor cannot trace (for example `read_files(...)`): in each case the node builds as plain dbt would. hodor never fails a dbt run.
+
+### Reason codes
+
+| Reason | Decision |
+| --- | --- |
+| `full_refresh` | build |
+| `unsupported` | build |
+| `no_history` | build |
+| `relation_missing` | build |
+| `code_changed` | build |
+| `config_changed` | build |
+| `target_modified` | build |
+| `select_star_view` | build |
+| `view_unchanged` | reuse |
+| `unknown_upstream` | build |
+| `no_new_data` | reuse |
+| `within_lag_tolerance` | reuse |
+| `new_upstream_data` | build |
+| `volatile_sql` | build |
+| `hodor_error` | build |
+
+The rules are checked in this order; the first match decides. `dbt-hodor explain -s <model>` shows the reason for one node, with the hashes and upstream data versions it compared. The full rules are in the [design spec](docs/design.md#5-decision-rules).
+
+## Modes
+
+| Mode | Behavior |
+| --- | --- |
+| `off` | hodor does nothing. |
+| `shadow` (default) | hodor decides and records, but every node builds. Use it to check the decisions before you trust them. |
+| `on` | hodor reuses nodes. |
+
+Installing the package never skips anything until someone sets `on`.
+
+## Configuration
+
+### Node configs
+
+hodor reads the same `state:` block as dbt State, so a project can switch between the two. Set it in YAML:
+
+```yaml
+# dbt_project.yml
+models:
+  my_project:
+    +state:
+      lag_tolerance: 4h
+      require_fresh_data_from: any
+```
+
+| Key | Default | Values |
+| --- | --- | --- |
+| `lag_tolerance` | `45m` | `0s`, `45m`, `4h`, `1d`, `1w`, integer seconds, or `{count: 4, period: hour}` |
+| `require_fresh_data_from` | `any` | `any`: build when any upstream has new data. `all`: build only when all of them have. |
+| `compare_unrendered_code` | `false` | `true`: build only when both the rendered and the unrendered code changed |
+| `execute_hooks_on_any_reuse` | `false` | `true`: run pre- and post-hooks on a reused node. `execute_hooks_on_reuse` is also accepted. |
+| `evaluate_volatile_sql` | auto | Auto: volatile functions such as `current_date()`, `current_user()` and `current_timestamp()` count as an upstream that changes, unless they only fill a stamp column. `true`: stamp columns count too. `false`: they never count (the dbt State default). |
+
+`pre_clone`, `allow_clones` and `defer_to_target` are accepted and ignored, with a warning.
+
+### Settings
+
+Set them on the `profiles.yml` target, or for one run with `--vars '{hodor_mode: off}'`. Precedence: environment variable, then `--vars`, then the profile key.
+
+| Profile key | Env var | Default | Values |
+| --- | --- | --- | --- |
+| `hodor_mode` | `HODOR_MODE` | `shadow` | `off`, `shadow`, `on` |
+| `hodor_store` | `HODOR_STORE` | `delta` | `delta`, `duckdb`, `postgres` (alias `lakebase`) |
+| `hodor_database` | `HODOR_DATABASE` | the target's `catalog` (or `database`) | Databricks catalog; Postgres database (later). Not used by `duckdb` |
+| `hodor_schema` | `HODOR_SCHEMA` | none for `delta` (required); `main` for `duckdb` | schema name |
+| `hodor_table` | `HODOR_TABLE` | `hodor_state` | table name |
+| `hodor_path` | `HODOR_PATH` | `.hodor/state.duckdb` | DuckDB database file, for `duckdb` |
+| `hodor_metadata_threads` | `HODOR_METADATA_THREADS` | `8` | 1-64 |
+| `hodor_lookback_days` | `HODOR_LOOKBACK_DAYS` | `90` | 1-3650 |
+
+Name parts may contain letters, digits, `_` and `-`. hodor always quotes them.
+
+### Where the state lives
+
+| Store | Location | Created on first use |
+| --- | --- | --- |
+| `delta` | `<hodor_database>.<hodor_schema>.<hodor_table>` | the table only. The schema must exist, because creating one needs catalog-level grants |
+| `duckdb` | table `<hodor_schema>.<hodor_table>` in the file `hodor_path` | the file, the schema and the table |
+| `postgres` (alias `lakebase`) | `<hodor_schema>.<hodor_table>` in the Postgres database `hodor_database` | the schema and the table |
+
+`delta` has no default schema on purpose: hodor writes nothing to a catalog until someone names the schema. Without it, hodor turns itself off with a warning.
+
+```yaml
+# profiles.yml
+my_project:
+  target: prod
+  outputs:
+    prod:
+      type: databricks
+      catalog: my_catalog
+      # ... connection settings ...
+      hodor_mode: shadow
+      hodor_schema: ops
+      # state table: my_catalog.ops.hodor_state
+    local:
+      type: duckdb
+      path: dev.duckdb
+      hodor_store: duckdb
+      # state table: main.hodor_state in .hodor/state.duckdb
+```
+
+The state table decides what gets skipped in prod. Grant `MODIFY` on it only to the job service principals.
+
+## Scope of v1
+
+Supported: models materialized as `table`, `incremental` (append, merge, delete+insert, insert_overwrite, replace_where; an unset strategy counts as merge) and `view`, seeds, snapshots, and data tests (generic and singular), on `dbt-databricks` 1.12.7 and `dbt-duckdb`, with dbt-core 1.12.x.
+
+Model versions: each version is its own node with its own table and records. Moving `latest_version` rebuilds the models that `ref()` it.
+
+Always built as plain dbt: clones and deferral, Python models, microbatch, materialized views, streaming tables, metric views, custom materializations, custom incremental strategies and unit tests.
+
+Known limit: a change to dbt's or the adapter's own macros, for example a dbt-databricks upgrade, does not show in any hash. Run once with `HODOR_MODE=off` after such an upgrade. Project and package macros that a materialization or a hook runs are in the config hash.
+
+## Development
+
+Requires [uv](https://docs.astral.sh/uv/). Local development and tests run on DuckDB, with no Databricks access.
+
+```sh
+uv sync
+uv run pytest
+uv run ruff check
+uv run ruff format
+```
+
+The live Databricks test is opt-in: see [docs/development.md](docs/development.md#tests).
+
+Build a wheel with `uv build`. The package is not published to any index yet.
+
+## Contributing
+
+Issues and pull requests are welcome. [CONTRIBUTING.md](CONTRIBUTING.md) has the setup, the
+checks to run, and what a decision change needs. A wrong reuse, where hodor skipped a node
+it should have rebuilt, is a security-grade bug: report it privately through the Security tab.
+
+## License
+
+Apache-2.0. [NOTICE](NOTICE) carries the attribution for the derived files and the trademark
+notice; [LICENSE](LICENSE) is the full licence text.

dbt_hodor-0.1.0/README.md

@@ -0,0 +1,187 @@
+<!-- markdownlint-disable MD033 MD041 -->
+<p align="center">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="docs/assets/hodor-logo.svg">
+    <img src="docs/assets/hodor-logo-light.svg" width="420" alt="dbt-hodor: Hold Old Data, Or Rebuild">
+  </picture>
+</p>
+
+<h1 align="center">dbt-hodor</h1>
+
+<p align="center">
+  <a href="https://github.com/alaturqua/dbt-hodor/actions/workflows/ci.yml"><img src="https://github.com/alaturqua/dbt-hodor/actions/workflows/ci.yml/badge.svg" alt="CI"></a>
+  <img src="https://img.shields.io/badge/python-3.10%20to%203.12-blue" alt="Python 3.10 to 3.12">
+  <img src="https://img.shields.io/badge/dbt--core-1.12-orange" alt="dbt-core 1.12">
+  <img src="https://img.shields.io/badge/license-Apache--2.0-green" alt="Apache-2.0">
+  <a href="https://alaturqua.github.io/dbt-hodor/"><img src="https://img.shields.io/badge/docs-online-informational" alt="Documentation"></a>
+</p>
+
+**[Documentation](https://alaturqua.github.io/dbt-hodor/)** | **[Interactive guide](https://alaturqua.github.io/dbt-hodor/guide/)** with a run simulator | **[Design spec](https://alaturqua.github.io/dbt-hodor/design/)**
+
+dbt-hodor is a free, self-hosted alternative to dbt Labs' [dbt State](https://docs.getdbt.com/docs/deploy/dbt-state-about). It runs inside dbt. For every selected node it decides whether to reuse the object that is already in the warehouse or to build it again. A node is reused when its logic has not changed and its upstream data has not changed since the last build.
+
+It needs no dbt platform account and sends nothing to external services. State lives in a Delta table on Databricks, in a Postgres database such as Databricks Lakebase, or in a local DuckDB file.
+
+> **Status: early development.** hodor runs inside dbt and passes end-to-end tests on dbt-duckdb. Tested live on a Databricks Unity Catalog workspace with a SQL warehouse and dbt-databricks 1.12.7 (2026-10-20 and 2026-10-21): reuse of tables, incremental models (including `replace_where`), views, seeds and snapshots, replayed tests, maintenance commits (OPTIMIZE, zero-row writes, SET TBLPROPERTIES) that keep nodes reused, and real new data or a changed seed file that rebuilds them. The live test runs twice, with `use_materialization_v2` off and on, and also covers contracts with a primary key, a row filter, column masks, date-window and stamp models, and a table swapped in by `use_safer_relation_operations`. The same live suite passes on a second, independent Databricks workspace (2026-10-21). The `postgres` store is tested end to end against Databricks Lakebase. It has not run in a large production project yet. Start in shadow mode.
+
+## Why "hodor"
+
+The name is a backronym: **H**old **O**ld **D**ata, **O**r **R**ebuild. That is the only decision hodor makes, once per node.
+
+hodor holds the door in front of your warehouse. A node gets through to a rebuild only when its code changed or new data arrived upstream. Everything else keeps the data it already has.
+
+## How it works
+
+For each node in `dbt run`, `dbt build`, `dbt test`, `dbt seed` or `dbt snapshot`, hodor:
+
+1. **Hashes the logic.** For a seed this is the CSV file. Otherwise the compiled SQL is normalized with [sqlglot](https://github.com/tobymao/sqlglot) (Databricks dialect), so case, quoting, comments and table aliases do not count as changes. Values that differ on every run, such as `invocation_id`, are replaced first. The node config is hashed as well.
+2. **Checks the upstream data.** Each upstream table has a data version. On Databricks it comes from the Delta commit history; maintenance commits such as `OPTIMIZE` or `VACUUM` do not count as data changes. On DuckDB it is a content fingerprint.
+3. **Decides.** It compares both against the record of the node's last build and returns `reuse` or `build`, with a reason code.
+4. **Records.** It appends one record per node to the state table.
+
+A run with no code changes skips sqlglot entirely: when the compiled SQL is byte-identical to the last build, hodor reuses the stored analysis. For 10,000 compiled models, hashing then takes about 0.1 seconds instead of about 4 minutes.
+
+### Safety: fail open
+
+Every failure leads to a build, never to a reuse. An error while deciding, a store that cannot be read, a table whose data version is unknown, an input hodor cannot trace (for example `read_files(...)`): in each case the node builds as plain dbt would. hodor never fails a dbt run.
+
+### Reason codes
+
+| Reason | Decision |
+| --- | --- |
+| `full_refresh` | build |
+| `unsupported` | build |
+| `no_history` | build |
+| `relation_missing` | build |
+| `code_changed` | build |
+| `config_changed` | build |
+| `target_modified` | build |
+| `select_star_view` | build |
+| `view_unchanged` | reuse |
+| `unknown_upstream` | build |
+| `no_new_data` | reuse |
+| `within_lag_tolerance` | reuse |
+| `new_upstream_data` | build |
+| `volatile_sql` | build |
+| `hodor_error` | build |
+
+The rules are checked in this order; the first match decides. `dbt-hodor explain -s <model>` shows the reason for one node, with the hashes and upstream data versions it compared. The full rules are in the [design spec](docs/design.md#5-decision-rules).
+
+## Modes
+
+| Mode | Behavior |
+| --- | --- |
+| `off` | hodor does nothing. |
+| `shadow` (default) | hodor decides and records, but every node builds. Use it to check the decisions before you trust them. |
+| `on` | hodor reuses nodes. |
+
+Installing the package never skips anything until someone sets `on`.
+
+## Configuration
+
+### Node configs
+
+hodor reads the same `state:` block as dbt State, so a project can switch between the two. Set it in YAML:
+
+```yaml
+# dbt_project.yml
+models:
+  my_project:
+    +state:
+      lag_tolerance: 4h
+      require_fresh_data_from: any
+```
+
+| Key | Default | Values |
+| --- | --- | --- |
+| `lag_tolerance` | `45m` | `0s`, `45m`, `4h`, `1d`, `1w`, integer seconds, or `{count: 4, period: hour}` |
+| `require_fresh_data_from` | `any` | `any`: build when any upstream has new data. `all`: build only when all of them have. |
+| `compare_unrendered_code` | `false` | `true`: build only when both the rendered and the unrendered code changed |
+| `execute_hooks_on_any_reuse` | `false` | `true`: run pre- and post-hooks on a reused node. `execute_hooks_on_reuse` is also accepted. |
+| `evaluate_volatile_sql` | auto | Auto: volatile functions such as `current_date()`, `current_user()` and `current_timestamp()` count as an upstream that changes, unless they only fill a stamp column. `true`: stamp columns count too. `false`: they never count (the dbt State default). |
+
+`pre_clone`, `allow_clones` and `defer_to_target` are accepted and ignored, with a warning.
+
+### Settings
+
+Set them on the `profiles.yml` target, or for one run with `--vars '{hodor_mode: off}'`. Precedence: environment variable, then `--vars`, then the profile key.
+
+| Profile key | Env var | Default | Values |
+| --- | --- | --- | --- |
+| `hodor_mode` | `HODOR_MODE` | `shadow` | `off`, `shadow`, `on` |
+| `hodor_store` | `HODOR_STORE` | `delta` | `delta`, `duckdb`, `postgres` (alias `lakebase`) |
+| `hodor_database` | `HODOR_DATABASE` | the target's `catalog` (or `database`) | Databricks catalog; Postgres database (later). Not used by `duckdb` |
+| `hodor_schema` | `HODOR_SCHEMA` | none for `delta` (required); `main` for `duckdb` | schema name |
+| `hodor_table` | `HODOR_TABLE` | `hodor_state` | table name |
+| `hodor_path` | `HODOR_PATH` | `.hodor/state.duckdb` | DuckDB database file, for `duckdb` |
+| `hodor_metadata_threads` | `HODOR_METADATA_THREADS` | `8` | 1-64 |
+| `hodor_lookback_days` | `HODOR_LOOKBACK_DAYS` | `90` | 1-3650 |
+
+Name parts may contain letters, digits, `_` and `-`. hodor always quotes them.
+
+### Where the state lives
+
+| Store | Location | Created on first use |
+| --- | --- | --- |
+| `delta` | `<hodor_database>.<hodor_schema>.<hodor_table>` | the table only. The schema must exist, because creating one needs catalog-level grants |
+| `duckdb` | table `<hodor_schema>.<hodor_table>` in the file `hodor_path` | the file, the schema and the table |
+| `postgres` (alias `lakebase`) | `<hodor_schema>.<hodor_table>` in the Postgres database `hodor_database` | the schema and the table |
+
+`delta` has no default schema on purpose: hodor writes nothing to a catalog until someone names the schema. Without it, hodor turns itself off with a warning.
+
+```yaml
+# profiles.yml
+my_project:
+  target: prod
+  outputs:
+    prod:
+      type: databricks
+      catalog: my_catalog
+      # ... connection settings ...
+      hodor_mode: shadow
+      hodor_schema: ops
+      # state table: my_catalog.ops.hodor_state
+    local:
+      type: duckdb
+      path: dev.duckdb
+      hodor_store: duckdb
+      # state table: main.hodor_state in .hodor/state.duckdb
+```
+
+The state table decides what gets skipped in prod. Grant `MODIFY` on it only to the job service principals.
+
+## Scope of v1
+
+Supported: models materialized as `table`, `incremental` (append, merge, delete+insert, insert_overwrite, replace_where; an unset strategy counts as merge) and `view`, seeds, snapshots, and data tests (generic and singular), on `dbt-databricks` 1.12.7 and `dbt-duckdb`, with dbt-core 1.12.x.
+
+Model versions: each version is its own node with its own table and records. Moving `latest_version` rebuilds the models that `ref()` it.
+
+Always built as plain dbt: clones and deferral, Python models, microbatch, materialized views, streaming tables, metric views, custom materializations, custom incremental strategies and unit tests.
+
+Known limit: a change to dbt's or the adapter's own macros, for example a dbt-databricks upgrade, does not show in any hash. Run once with `HODOR_MODE=off` after such an upgrade. Project and package macros that a materialization or a hook runs are in the config hash.
+
+## Development
+
+Requires [uv](https://docs.astral.sh/uv/). Local development and tests run on DuckDB, with no Databricks access.
+
+```sh
+uv sync
+uv run pytest
+uv run ruff check
+uv run ruff format
+```
+
+The live Databricks test is opt-in: see [docs/development.md](docs/development.md#tests).
+
+Build a wheel with `uv build`. The package is not published to any index yet.
+
+## Contributing
+
+Issues and pull requests are welcome. [CONTRIBUTING.md](CONTRIBUTING.md) has the setup, the
+checks to run, and what a decision change needs. A wrong reuse, where hodor skipped a node
+it should have rebuilt, is a security-grade bug: report it privately through the Security tab.
+
+## License
+
+Apache-2.0. [NOTICE](NOTICE) carries the attribution for the derived files and the trademark
+notice; [LICENSE](LICENSE) is the full licence text.