You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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-spark functionality, rather than a Big Idea better suited to a discussion
Describe the feature
Given that Databricks users have largely adopted dbt-databricks, we do not need to test these profiles on dbt-spark. Removing these profiles will also result in removing some tests that are only run on these profiles. It is not clear how far back we should implement this change (e.g. is this 1.7+? all supported versions? somewhere in between?)
Describe alternatives you've considered
No response
Who will this benefit?
This will benefit the maintainers as CI run times will be drastically reduced. This will also enable more rapid review and implementation of community PRs, which should deliver more value to our users.
Are you interested in contributing this feature?
Yes
Anything else?
No response
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
[Feature] Remove Databricks test profiles from integration tests
[ADAP-1018] [Feature] Remove Databricks test profiles from integration tests
Nov 7, 2023
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.
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.
Is this your first time submitting a feature request?
Describe the feature
Given that Databricks users have largely adopted
dbt-databricks
, we do not need to test these profiles ondbt-spark
. Removing these profiles will also result in removing some tests that are only run on these profiles. It is not clear how far back we should implement this change (e.g. is this 1.7+? all supported versions? somewhere in between?)Describe alternatives you've considered
No response
Who will this benefit?
This will benefit the maintainers as CI run times will be drastically reduced. This will also enable more rapid review and implementation of community PRs, which should deliver more value to our users.
Are you interested in contributing this feature?
Yes
Anything else?
No response
The text was updated successfully, but these errors were encountered: