Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dbt clean in migration guide for v1.7 #5121

Merged
merged 5 commits into from
Mar 21, 2024
Merged

Update dbt clean in migration guide for v1.7 #5121

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e2a25bd
Update dbt clean in migration guide for v1.7
matthewshaver Mar 19, 2024
4dd3cec
Update website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1…
matthewshaver Mar 21, 2024
1cb02d3
Update website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1…
matthewshaver Mar 21, 2024
5b542ed
Merge branch 'current' into clean
matthewshaver Mar 21, 2024
3503317
Merge branch 'current' into clean
matthewshaver Mar 21, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion website/docs/docs/dbt-versions/core-upgrade/02-upgrading-to-v1.7.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,16 @@ dbt Core v1.5 introduced model governance which we're continuing to refine. v1.
- **[Breaking change detection](/reference/resource-properties/versions#detecting-breaking-changes) for models with contracts enforced:** When dbt detects a breaking change to a model with an enforced contract during state comparison, it will now raise an error for versioned models and a warning for models that are not versioned.
- **[Set `access` as a config](/reference/resource-configs/access):** You can now set a model's `access` within config blocks in the model's file or in the `dbt_project.yml` for an entire subfolder at once.
- **[Type aliasing for model contracts](/reference/resource-configs/contract):** dbt will use each adapter's built-in type aliasing for user-provided data types—meaning you can now write `string` always, and dbt will translate to `text` on Postgres/Redshift. This is "on" by default, but you can opt-out.
- **[Raise warning for numeric types](/reference/resource-configs/contract):** Because of issues when putting `numeric` in model contracts without considering that default values such as `numeric(38,0)` might round decimals accordingly. dbt will now warn you if it finds a numeric type without specified precision/scale.
- **[Raise warning for numeric types](/reference/resource-configs/contract):** Because of issues when putting `numeric` in model contracts without considering that default values such as `numeric(38,0)` might round decimals accordingly. dbt will now warn you if it finds a numeric type without specified precision/
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved
scale.
matthewshaver marked this conversation as resolved.
Show resolved Hide resolved

### dbt clean

Starting in v1.7, `dbt clean` will only clean paths within the current working directory. The `--no-clean-project-files-only` flag will delete all paths specified in `clean-paths`, even if they're outside the dbt project.

Supported flags:
- `--clean-project-files-only` (default)
- `--no-clean-project-files-only`

### Additional attributes in run_results.json

Expand Down
Loading