The dbt clone command, whereby dbt can clone nodes based on their location in the manifest provided to the -state flag.Deferring to another environment, whereby dbt can identify upstream, unselected resources that don't exist in your current environment and instead "defer" their references to the environment provided by the state manifest.
#Ls models collection code#
The state: selector, whereby dbt can identify resources that are new or modifiedīy comparing code in the current project against the state manifest.Crucially, the operations themselves are still stateless and idempotent: given the same manifest and the same raw data, dbt will produce the same transformed result.ĭbt can leverage artifacts from a prior invocation as long as their file path is passed to the -state flag.
If you choose, dbt can use these artifacts to inform certain operations.
That said, dbt does store "state"-a detailed, point-in-time view of project resources (also referred to as nodes), database objects, and invocation results-in the form of its artifacts. A given run of dbt doesn't need to "know" about any other run it just needs to know about the code in the project and the objects in your database as they exist right now. Given the same raw data, you can expect the same transformed result. It doesn't matter if you run it once or a thousand times. That is, it doesn't matter how many times a model has been run before, or if it has ever been run before. One of the greatest underlying assumptions about dbt is that its operations should be stateless and idempotent.
a selection method ( path:, tag:, config:, test_type:, test_name:). a fully-qualified path to a directory of models. The -select flag accepts one or more arguments. Note that the following arguments ( -select, -exclude, and -selector) also apply to other dbt tasks, such as test and build. Use the -select flag with dbt run to select a subset of models to run. During development (and deployment), it is useful to specify only a subset of models to run. Select resources to build (run, test, seed, snapshot) or check freshness: -select, -s Examples īy default, dbt run will execute all of the models in the dependency graph. (Only seeds are kept for dbt seed, only models for dbt run, only tests for dbt test, and so on.) As a final step, it tosses away any resource that does not match the resource type of the current task. (Tests can also be selected "indirectly" via their parents see test selection examples for details.)ĭbt now has a list of still-selected resources of varying types. The selected resources may be models, sources, seeds, snapshots, tests. +), then finally set operators ( unions, intersections, exclusions). How does selection work? ĭbt gathers all the resources that are matched by one or more of the -select criteria, in the order of selection methods (e.g. The -select flag is used to specify a subset of nodes to execute. Specifying resources īy default, dbt run executes all of the models in the dependency graph dbt seed creates all seeds, dbt snapshot performs every snapshot. They are the objects that make up dbt's DAG (directed acyclic graph). These encompass all the models, tests, sources, seeds, snapshots, exposures, and analyses in your project. We use the terms "nodes" and "resources" interchangeably.
0 kommentar(er)
