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

[Feature][Spike] Allow adapters to specify multiple namespaces #10280

Closed
3 tasks done
colin-rogers-dbt opened this issue Jun 7, 2024 · 2 comments
Closed
3 tasks done
Labels
enhancement New feature or request stale Issues that have gone stale triage

Comments

@colin-rogers-dbt
Copy link
Contributor

Is this your first time submitting a feature request?

  • I have read the expectations for open source contributors
  • I have searched the existing issues, and I could not find an existing issue for this feature
  • I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature

Currently an adapter can supply only one namespace prefix for macros. This poses a challenge if we want to sever/deprecate inheritance relationships for adapters while maintaining backwards compatibility (i.e. dbt-redshift and dbt-postgres). Instead we'd like an adapter to be able to supply the deprecated parent adapters namespace along with it's own.

Relevant code section: https://github.com/dbt-labs/dbt-core/blob/main/core/dbt/context/providers.py#L143

Describe alternatives you've considered

No response

Who will this benefit?

No response

Are you interested in contributing this feature?

No response

Anything else?

No response

@colin-rogers-dbt colin-rogers-dbt added enhancement New feature or request triage labels Jun 7, 2024
@colin-rogers-dbt colin-rogers-dbt changed the title [Feature] Allow adapters to specify multiple namespaces [Feature][Spike] Allow adapters to specify multiple namespaces Jun 21, 2024
Copy link
Contributor

This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please comment on the issue or else it will be closed in 7 days.

@github-actions github-actions bot added the stale Issues that have gone stale label Dec 19, 2024
Copy link
Contributor

Although we are closing this issue as stale, it's not gone forever. Issues can be reopened if there is renewed community interest. Just add a comment to notify the maintainers.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request stale Issues that have gone stale triage
Projects
None yet
Development

No branches or pull requests

1 participant