-
Notifications
You must be signed in to change notification settings - Fork 26
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
Tests Being Put into Own "tests_schema" #168
Comments
It's not expected for tests to create views, and certainly not outside the specified schema. in this case my schema is |
Hi @prdpsvs as requested via Slack here's a repro:
error
|
@ernestoongaro , I looked into these errors.
I will close this issue for now. Hope this helps. |
@prdpsvs I just updated to 1.8.4. The schema dbt_test__audit is not auto generated. 12:11:16 Database Error in test date_is_not_in_future_latest_inventory_movement_latest_inventory_movement (models\marts_marts_models.yml) |
By way of explanation: On every run, For some time, we've had conditional logic within I think there are two mitigation paths forward:
We could change the default Longer-term, it would be ideal for @prdpsvs I recommend reopening this issue in the meantime, while we sort out the appropriate mitigation. |
@jtcohen6 , @ernestoongaro , I did not address this completely but dbt-fabric 1.8.6 creates target schema |
Hello! I have some standard tests in my project, starting with dbt-fabric 1.8 this is what's happening:
The text was updated successfully, but these errors were encountered: