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

[Bug] Update tests: -> data_tests #65

Open
2 of 4 tasks
kolbynelson opened this issue Jun 7, 2024 · 6 comments
Open
2 of 4 tasks

[Bug] Update tests: -> data_tests #65

kolbynelson opened this issue Jun 7, 2024 · 6 comments
Labels
type:wontfix This will not be worked on

Comments

@kolbynelson
Copy link

kolbynelson commented Jun 7, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Describe the issue

On dbt version 1.8+ the tests: config results in a warning and needs to be replaced with the data_tests: config.

Relevant error log or model output

[WARNING]: Deprecated functionality
The `tests` config has been renamed to `data_tests`. Please see https://docs.getdbt.com/docs/build/data-tests#new-data_tests-syntax for more information.

Expected behavior

Do not warn.

dbt Project configurations

version: '1.8.1'

Package versions

packages:

  • package: fivetran/google_ads
    version: [">=0.10.0", "<0.11.0"]
  • package: fivetran/sage_intacct
    version: [">=0.4.0", "<0.5.0"]

What database are you using dbt with?

snowflake

dbt Version

version: '1.8.1'

Additional Context

This is especially an issue when combined with the --warn-error flag. In order for dbt Cloud to send email notifications about test warnings we use the command dbt --warn-error test command. The rest of our tests do not run due to this deprecation warning in the package.

Are you willing to open a PR to help address this issue?

  • Yes.
  • Yes, but I will need assistance and will schedule time during our office hours for guidance
  • No.
@fivetran-joemarkiewicz
Copy link
Contributor

Hi @kolbynelson thanks for raising this issue.

Updating the tests to data_tests is something that is on our radar to update across the Fivetran dbt packages in the near future. However, we will want to make this update to all our packages at the same time as this update will make our packages not compatibile with dbt-core<1.8.0 versions 😰.

That being said, the issue you are describing sounds like an unexpected behavior of dbt-core. I would expect while the tests config is still accepted, you should not be seeing this type of compilation failure which causes all your other tests to not run. I just opened an issue in dbt-core to see if this is an expected behavior. I will follow along there and determine if there are any immediate updates we need to make to our data model, or if this should be addressed in dbt-core.

Thanks!

@fivetran-joemarkiewicz
Copy link
Contributor

@kolbynelson it looks like dbt Labs was able to respond to the above dbt-core issue I opened and are suggesting you use the following command as opposed to dbt --warn-error test.

dbt --warn-error-options '{"error": "all", "silence": ["TestsConfigDeprecation"]}' test

This should resolve the compilation you are seeing and allow you to continue leveraging this solution prior to the Fivetran dbt packages being updated to support the new data_tests naming convention. Let me know if this helps!

@fivetran-joemarkiewicz fivetran-joemarkiewicz added the status:scoping Currently being scoped label Jun 7, 2024
@fivetran-joemarkiewicz
Copy link
Contributor

@kolbynelson let me know if the above addresses your concerns. As there is not something we will address here for the moment in the dbt package I will mark this as won't do. However, I will keep this open as we will plan to make this update in the future months. Thanks!

@fivetran-joemarkiewicz fivetran-joemarkiewicz added type:wontfix This will not be worked on and removed status:scoping Currently being scoped labels Jun 12, 2024
@kolbynelson
Copy link
Author

kolbynelson commented Jun 12, 2024 via email

@fivetran-joemarkiewicz
Copy link
Contributor

Hi @kolbynelson,

I am sorry to hear that didn't work. Unfortunately I am not entirely familiar with the nuances of dbt Cloud in this context. I would recommend reviewing the suggestions from the issue I opened on dbt Core. It looks like there are a few other options you can take here as suggested by dbt Labs. If this doesn't work, I would advise commenting in the issue I created on dbt Labs to see if the folks there are able to provide guidance on possible next steps.

@kolbynelson
Copy link
Author

kolbynelson commented Jun 12, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants