-
Notifications
You must be signed in to change notification settings - Fork 105
Remove Fabric Dependency #628
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
base: master
Are you sure you want to change the base?
Remove Fabric Dependency #628
Conversation
The 'functional' target in the Makefile now accepts an optional THREADS parameter. If no THREADS value is supplied, it defaults to 'auto'. This allows users to specify the number of parallel test threads, addressing potential resource issues like SQL Server running out of memory when many tests run concurrently.
…rather than taking all the cores.
…sql version of the adapter as the upstream testing was relied on. Fix snapshot logic not being updated to 1.9 to pass tests. Fix issues with the test failure storage tests related to expected errors due to bad model naming.
for more information, see https://pre-commit.ci
|
@Benjamin-Knight I am just an extremely happy user of this adapter but if there is something I could potentially help with please let me know and I will check with my employer if I can carve out some time to work, do tests, etc on this adapter. |
Right now we are kind of on hold until a maintainer appears. |
This pull request is a big one that aims to remove the dependency this adapter has on the dbt-fabric adapter.
As Fabric drifts further from SQL server it will become increasingly difficult to keep Fabric as a base, its also still on version 1.9.
I've also looked at the work @axellpadilla has been doing recently and added in the CI work to support python 3.13 with a view to bumping this adapter up to version 1.11 to match the current DBT core release.
@cody-scott As the most recently active maintainer are you able to help progress this issue or hand additional rights to myself or @axellpadilla to see if we can start closing off some of the issues on this adapter?
In terms of the pull request as its a big one the more eyes on it the better, I've ported over some of the functional tests from Fabric that were not implemented in this adapter to try and keep coverage up and all current functional tests we had are passing. I think we may still want to do a beta release however.