Closed dubravcik closed 3 years ago
No current plans to implement this as I have no use case for it, but feel free to implement it and contribute. The codebase is pretty small and easy to follow :)
@z3z1ma I think your recent PRs implement this, right? Thinking of closing this issue.
Yes that's right @gouline . We resolved this for both parsers using a hash key.
We allow no schema passed so long as user is using manifest parser since we can reliably resolve schema in all cases to construct the schema.table hash.
Folder parser is multi schema compliant only with multiple invocations (one per schema since we need the arg to construct the hash) and even then I'm sure I could imagine nuances that make manifest parser superior for model propagation.
We are using multiple schemas specified in dbt_project.yml. It would be great if dbt-metabase follows the schema settings and does not send everything to the schema from the command line.
thanks @gouline :)