lightdash: There should be some 'blocking' and 'non-blocking' errors in the CLI `lightdash preview`
Description
Right now, if I’m developing my Lightdash project, I might not have all of the tables in my project existing in my development space. I’ll probably just have the tables I’m working on that are in BigQuery (e.g. I’m working on users, I’ll probably have everything upstream + downstream from that in my available tables)
But, the Lightdash CLI won’t let me preview the instance if I don’t have all of the tables in my project available.
Basically, I’d expect the preview to work the same way as my current project: if some tables are missing, they’d just be greyed out (and I might get some notification of this on the CLI tool). If the project is broken, I would get an error saying that the project was broken and I couldn’t preview it.
What problem does this solve?
I can’t really use lightdash preview when I’m developing if I’m working in a huge project.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (8 by maintainers)
oh nice! Okay, maybe this got fixed - I’m not sure…i’ll see if I can replicate it again somewhere 👀
Yeah I think it depends. Whatever we need to speed up dev I’m for it.
I can add a new ticket. Also I think this is very closely related to #2499
👀 I’ll say!!!
In this case the error comes from automatically figuring out the dimension and there’s an inconsistency because when users hit “refresh dbt” in the UI we assume that missing dimensions are of string type. But it seems like there’s a bug in the CLI where it’s still returning errors instead of just defaulting to strings.
I think that’s the most common error we’ve seen among
lightdash previewusers too