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

Migrate to using decoupled new decoupled core/adapters architecture #585

Closed
colin-rogers-dbt opened this issue Feb 15, 2024 · 2 comments
Closed
Labels
enhancement New feature or request Stale

Comments

@colin-rogers-dbt
Copy link
Contributor

colin-rogers-dbt commented Feb 15, 2024

Describe the feature

Opening this issue to track dbt-databricks decoupling migration and provide additional guidance/context.

Specific recommendations:

Describe alternatives you've considered

Not doing this will block dbt-databricks from working with post 1.8 dbt-core versions.

Additional context

N/A

Who will this benefit?

All dbt-databricks users and maintainers!

Are you interested in contributing this feature?

Happy to help out however we can.

@colin-rogers-dbt colin-rogers-dbt added the enhancement New feature or request label Feb 15, 2024
@benc-db
Copy link
Collaborator

benc-db commented Feb 15, 2024

Ack, thanks for filing

Copy link

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 remove the stale label or comment on the issue.

@github-actions github-actions bot added the Stale label Aug 14, 2024
@benc-db benc-db closed this as completed Oct 3, 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
Projects
None yet
Development

No branches or pull requests

2 participants