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.

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

[Core] Upgrade guide for model names that contain spaces #5347

Closed
dbeatty10 opened this issue Apr 24, 2024 · 0 comments · Fixed by #5351
Closed

[Core] Upgrade guide for model names that contain spaces #5347

dbeatty10 opened this issue Apr 24, 2024 · 0 comments · Fixed by #5351
Labels
content Improvements or additions to content dbt Core The changes proposed in this issue relate to dbt Core dbt-core v1.8

Comments

@dbeatty10
Copy link
Contributor

dbeatty10 commented Apr 24, 2024

Link to the page(s) on docs.getdbt.com requiring updates

Migration guide for v1.8

Tell us more about this update

For folks that have a model name that contains spaces, provide instructions for how to upgrade via custom aliases.

Before

models/my model.sql

select 1 as id

models/_models.yml

models:
  - name: "my model"

After - option 1

models/my_model.sql

{{ config(alias="my model") }}

select 1 as id

models/_models.yml

models:
  - name: "my model"

After - option 2

models/my_model.sql

select 1 as id

models/_models.yml

models:
  - name: my_model
    config:
      alias: "my model"

Reviewers/Stakeholders/SMEs

.

Related GitHub issues

Additional information

No response

@dbeatty10 dbeatty10 added content Improvements or additions to content dbt Core The changes proposed in this issue relate to dbt Core dbt-core v1.8 labels Apr 24, 2024
dbeatty10 added a commit that referenced this issue Apr 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content dbt Core The changes proposed in this issue relate to dbt Core dbt-core v1.8
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant