An entry under targets in databricks.yml describing one deployment and layering its values over the top-level ones. If a setting appears in both, the target's value is used.
Read more: Databricks docs
In the Ultra Transcenders books
Each book explains Bundle target in context, with comparison tables and the common traps.
Terms in this definition
- databricks.yml
Every bundle needs this configuration file in its project's root folder. It sets the bundle's name and targets, and its
includesetting brings in further configuration files. - Model deployment
Inside a resource, each deployment is a named copy of a Foundry model with its own TPM quota and deployment type. Requests identify the model by this deployment name.
- VALUES
Returns in DAX the distinct column values, or table rows, still visible after filters are applied, sometimes with an extra blank entry. CALCULATE often takes the result as a table filter.
- OVER
Gives a T-SQL window function its window: PARTITION BY, ORDER BY and, if wanted, a ROWS or RANGE frame. Rankings and running totals can then be worked out while every row is kept.
Related terms
- Bundle deployment modes
Two optional presets for a bundle target,
mode: developmentandmode: production, each of which switches on a set of settings together. - Presets
Settings in a bundle target, such as
name_prefix,trigger_pause_status,pipelines_development,jobs_max_concurrent_runsandtags, that adjust or replace the defaults of a deployment mode; anything set on a resource itself beats a preset.