Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support wildcard column names

See original GitHub issue

Description: What is it?

Some schema.yml files use wildcards to add documentation to all columns in a schema file, for example: https://github.com/brooklyn-data/dbt_artifacts/blob/0127c460733299827af3456daa88fa3dc8927bda/models/schemas.yml#L132-L133

This isn’t supported by Lightdash, it would be great if it worked!

Problem: What problem does this solve?

(Optional) Why: How do we know this is a real problem and worth solving?

What: Roughly, what does this look like in the product?

Issue Analytics

State:
Created a year ago
Comments:12 (8 by maintainers)

Top GitHub Comments

2reactions

ZeRegocommented, Aug 8, 2022

@TuringLovesDeathMetal Even if we supported the wild card we would only display the new dimensions when they click refresh dbt. I imagine this problem being solve by using our CLI in their CI/CD pipeline. Compiling and deploying the latest dbt project each time they merged something into their main branch or with a cron job.

1reaction

TuringLovesDeathMetalcommented, Aug 16, 2022

hmm, okay, the benefits of not supporting this seem to heavily outweigh the costs.

unless a bunch more users request this, I say we put this on hold for now. I’ll remove it from the backlog