You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
running exposure_schema_validity will yield this warning for each exposure and column
Warning - missing node property for the exposure: <exposure> which not the only exposure depending on <model>, We're not able to verify the column level dependencies of this exposure
To Reproduce
create a simple setup with exposure_a, exposure_b and model_x as described above
Expected behavior
no warning, since model_x is the only model in the depends_on of each exposure, therefore no node property should be needed
Screenshots
n/a
Environment
Elementary CLI (edr) version: 0.15.1
Elementary dbt package version: 0.15.2
dbt version you're using: 1.8.7
Data warehouse: databricks
Infrastructure details: n/a
Additional context
the test passes despite the warning
Would you be willing to contribute a fix for this issue?
if time allows
The text was updated successfully, but these errors were encountered:
Hi @data-blade !
Thanks for opening this issue, it indeed looks to me like a bug - it seems that what we're currently checking is whether or not there is more than one exposure depending on the same node, but I'm not sure why that is the check.
It may take us a bit of time to get to so if you're willing to contribute a fix will be happy to point to give pointers on where to look.
Describe the bug
given
exposure_a
andexposure_b
,each with just
model_x
in theirdepends_on
,each only specifying
column_name
.running
exposure_schema_validity
will yield this warning for each exposure and columnTo Reproduce
create a simple setup with
exposure_a
,exposure_b
andmodel_x
as described aboveExpected behavior
no warning, since
model_x
is the only model in thedepends_on
of each exposure, therefore nonode
property should be neededScreenshots
n/a
Environment
Additional context
the test passes despite the warning
Would you be willing to contribute a fix for this issue?
if time allows
The text was updated successfully, but these errors were encountered: