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

Jump to bottom

Namespacing: models with same name across projects/packages #3571

Closed
Tracked by #3362
jtcohen6 opened this issue Jun 20, 2023 · 0 comments · Fixed by #3604
Closed
Tracked by #3362

Namespacing: models with same name across projects/packages #3571

jtcohen6 opened this issue Jun 20, 2023 · 0 comments · Fixed by #3604
Assignees
@jtcohen6
Labels
content Improvements or additions to content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows
Milestone
dbt Core v1.6 Doc...

Comments

@jtcohen6
Copy link
Collaborator

jtcohen6 commented Jun 20, 2023 •
edited
Loading

Pages needing update:

dbt-core PR:
@jtcohen6 jtcohen6 mentioned this issue Jun 20, 2023
Closed
@jtcohen6 jtcohen6 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear idea Proposes an idea for new content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) labels Jun 20, 2023
@jtcohen6 jtcohen6 added this to the dbt Core v1.6 Documentation milestone Jun 20, 2023
@jtcohen6 jtcohen6 self-assigned this Jun 22, 2023
@runleonarun runleonarun added the priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows label Jun 22, 2023
@jtcohen6 jtcohen6 mentioned this issue Jun 24, 2023
Merged
4 tasks
jtcohen6 added a commit that referenced this issue Jun 26, 2023
@jtcohen6
Updates on model namespacing & uniqueness (#3604)
4170337 
resolves #3571

## What are you changing in this pull request and why?

Starting in v1.6, model names can be duplicated across different
namespaces (packages/projects). They must still be unique within one
package/project.

This requires updates to:
- our FAQ on model name uniqueness
- two-argument `ref`
- note on snapshot name uniqueness
- (I'm sure I've missed some places)

## Checklist
- [x] Add versioning components, as described in [Versioning
Docs](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-entire-pages)
- [x] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/guides/migration/versions)
- [x] Review the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
and [About
versioning](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
so my content adheres to these guidelines.
- [x] Add a checklist item for anything that needs to happen before this
PR is merged, such as "needs technical review" or "change base branch."
@runleonarun runleonarun removed the idea Proposes an idea for new content label Mar 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jtcohen6 jtcohen6

Labels
content Improvements or additions to content dbt-core v1.6 Docs impact for the v1.6 release (July 2023) improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows
Projects
None yet
Milestone
dbt Core v1.6 Documentation
Development

Successfully merging a pull request may close this issue.

Updates on model namespacing & uniqueness dbt-labs/docs.getdbt.com
2 participants
@runleonarun @jtcohen6