Open mjirv opened 2 years ago
Hmm, I believe that it's because your dbt model doesn't have meta.metriql
property and since Metriql ignores these dbt resources, it's not able to resolve the reference. I just added a warning here: https://metriql.com/reference/dataset/
That being said, it seems to be an edge case that we need to think about. What do you think about the best approach? Maybe we can allow other entities to resolve references but don't map them as datasets?
Oh I see, I didn't realize I needed to add that. Thank you!
To me, it would make sense to parse the dependencies but not expose them, like you say.
FYI that it looks like your warning isn't being rendered correctly.
I have a (valid) dbt metric defined as follows:
When running
metriql serve
I get the following error:I have a model named
orders
, randbt compile
just before runningmetriql serve
, and confirmed theorders
model is in mymanifest.json
.Changing quotation styles and including the package name did not help.
Version/environment
This is using Docker with
docker pull buremba/metriql:latest