You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e350e72
Browse filesBrowse the repository at this point in the historyBrowse files
refactor: move the plan layer of the Python bindings into sqlbuild-python-planner (#1523)
* refactor: move planner scope resolution and the cost context below the plan layer
The plan layer moves into its own crate next. Two pieces it uses sat in
sqlbuild-python although their layer is lower: the planner scope
resolution (project layer) and the cost attribution context (front
layer). They now live in sqlbuild-python-project and
sqlbuild-python-front, and their callers import them from there.
* refactor: move the plan layer of the Python bindings into sqlbuild-python-planner
Work in progress: the move itself. main/ forwarders are not folded yet,
and the field-fallback list, duplicate allowlist and crate README are
not updated.
* refactor: fold planner forwarders and regroup imports
* refactor: fit the planner crate to the lint, duplicate and fallback checks
* fix: key the dynamic planner field reads to their call site and correct the register allowlist reason
Copy file name to clipboardExpand all lines: crates/README.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,14 +31,15 @@ tested and benchmarked with `cargo test` alone.
31
31
|`sqlbuild-python-base`| The base of the PyO3 bindings: native record, enum and error classes with their specs, registration, construction and field reads; keyword calls, imports, conversions and panics at the Python boundary; host entry calls; the process allocator; and the shared runtime the binding modules build on: the native store, compile context, diagnostics, progress and terminal text, warehouse access and orchestration reads. |
32
32
|`sqlbuild-python-front`| The front of the compile pipeline as PyO3 bindings, on top of `sqlbuild-python-base`: project discovery, model configuration and headers, scopes, macro rendering and authored values, SQL text, model attachment and the compile driver, cursors, contract and refactor facts, and the warehouse state tables of consumption, observations and audit results. |
33
33
|`sqlbuild-python-project`| The compiled project as PyO3 bindings, on top of `sqlbuild-python-front`: the project host and the Python views of compiled models, inputs and resources, the compiled-project snapshot, analysis classes and the analysis session, the project graph, references, lineage, fingerprints, contracts and semantic shapes, audit rendering, and the planner's identities, scope, selection, phases, fixture strategy and SQL test planning. |
34
-
|`sqlbuild-python`| The `_native` module: its Python classes and functions and the conversions from Python objects, on top of `sqlbuild-python-project`, `sqlbuild-python-front` and `sqlbuild-python-base`. |
34
+
|`sqlbuild-python-planner`| The plan layer as PyO3 bindings, on top of `sqlbuild-python-project`: execution plans and their entries, planner phases, change detection, migrations, reference and cursor resolution, scenarios, strategy and warehouse inspection, plus freshness, consumption, microbatches, observations, lifecycle events and plan output. |
35
+
|`sqlbuild-python`| The `_native` module: its Python classes and functions and the conversions from Python objects, on top of `sqlbuild-python-planner`, `sqlbuild-python-project`, `sqlbuild-python-front` and `sqlbuild-python-base`. |
35
36
36
37
## Layering
37
38
38
39
Dependencies point one way, from the top of this graph to the bottom:
0 commit comments