Comments (6)
@gwenwindflower I just verified this is happening when you run without partial parsing. It's actually the integration tests that get shipped with the package that are causing the deprecation warning.
from dbt-core.
@gwenwindflower I just verified this is happening when you run without partial parsing. It's actually the integration tests that get shipped with the package that are causing the deprecation warning.
To expand on this further, the warning will disappear if dbt is able to do partial parsing -- since it skips over parsing the YAML in that case, it won't "see" the deprecated name... 🙈 🙉 🙉.
You'll be able to get the warning back by adding the --no-partial-parse
flag to any dbt command 🐵
from dbt-core.
Closing this as a non-issue, I was misreading the warning and misinterpreted the problem. Can confirm now that I understand and updated accordingly, the warning is gone. We are not in fact bubbling up warnings from packages.
from dbt-core.
@gwenwindflower not really. I did update everything in my project, so there is not a single test
config there either in the dbt_project.yml
or in the other yaml files where the tests are defined.
Only place were tests:
exists is inside dbt_packages
folder, it is, the packages code. In the tests that the packages have defined.
only way to get rid of that warning is by replacing inside dbt_packages all tests:
by data_tests:
which, of course, is just to confirm my hypothesis as that code shouldn't be modified.
from dbt-core.
@gwenwindflower are we sure about it? I'm updating to 1.8 and I'm getting the warning each single time. The only way I have to get rid of the warning is to manually update the config of the packages in the dbt_packages
folder from tests
to data_tests
.
Please check the following example where:
- I get the warning
- I manually update the config on the dbt_packages folder (only manual update done outside of the console log in the screenshot)
- I run dbt clean to remove dbt_packages folder
- dbt deps to re-create the code from the packages
- I get the warning again at compile time.
Is there anything else outside of the warning being triggered from the packages I may be missing?
Thanks!
from dbt-core.
@roman-segador any chance you were updating the directory name and/or dbt_project.yml
path and not the YAML config key names? that's what i was doing that had me confused.
from dbt-core.
Related Issues (20)
- [Feature] Add `--fail-if-nothing-selected` (or something similar) HOT 6
- [Bug] Not able to select unit tests via the `--resource-type` flag HOT 4
- Minor main.yml Improvements
- Unit Tests in 1.8.1 do not honor quoting on the descriptors for columns HOT 1
- [Bug] `TypeError: can not serialize 'Undefined' object` dbt=1.8.2 and databricks 1.8.0 HOT 5
- [Bug] Unit test names aren't required to be unique, and duplicates get swallowed HOT 2
- [Bug] Test description empty in manifest.json HOT 1
- [Bug] dbt --warn-error test results in compilation error when tests are not yet renamed on dbt-core>=1.8.0 HOT 2
- [Bug] state:modified.macros can detect false positives if package macro has same name as builtin (even though it won't be used)
- [Bug] `warn_error_options.silence` not working within `dbt_project.yml` HOT 1
- [Feature] Make warning and error classes more discoverable
- [Feature] Allow adapters to specify multiple namespaces
- [Bug] Unhelpful exception occurs with yaml file in list format HOT 1
- Use, and extend as necessary, happy path fixture for `tests/functional/artifacts/test_artifacts.py`
- Create parameterized test which tries each resource type with the `resource_type:` selector
- Use, and extend as necessary, happy path fixture for `tests/functional/graph_selection/test_graph_selection.py`
- [Bug] "no loader for this environment specified" when running a simple macro HOT 3
- [Bug] Cannot run unit test with duckdb as database HOT 3
- [Bug] dbt config format HOT 1
- saved queries are not included in the "modified" selector
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dbt-core.