-
Notifications
You must be signed in to change notification settings - Fork 146
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
elementary.schema_changes_from_baseline Test Fails for Certain Source Tables #1460
Comments
Hi @ahmedhamidibr ! Is this issue still relevant to you? |
Hi @haritamar, Yes, indeed, my project overrides the source macro. It turns out that was the cause. After resetting back to the default source macro, it worked as expected. However, I remain interested in any workaround you might suggest to ensure the tests continue to work even when the source macro is overridden. |
Hi @ahmedhamidibr , So there are two workarounds that can be done until we support this use case, depending on what exactly your overriding
|
@haritamar Thank you so much, this did the trick! |
Glad to hear @ahmedhamidibr ! |
Describe the bug
The issue arises when executing schema_changes_from_baseline test on source tables, it works for some tables and fails for others . For example:
Despite the tables sharing the same schema, the test fails for one table while succeeding for another. This inconsistency is observed even though both tables are defined with the same columns and data types in the dbt project's schema configuration. The error am getting is :
To Reproduce
Steps to reproduce the behavior:
dbt run-operation elementary.generate_schema_baseline_test --args '{"name": "source_table"}'
dbt test --select source:raw.source_table
Expected behavior
The elementary.schema_changes_from_baseline test should run successfully for all source tables, provided that all columns and their respective data types are accurately defined in the table configurations.
Environment (please complete the following information):
pip show elementary-data
packages.yml
fileThe text was updated successfully, but these errors were encountered: