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
Kimball came with a matrix overview to map business processes and shared dimensions. There are multiple variants as dw matrix, information matrix but in relation with dbt models the most useful would be matrix of fact tables on rows and dimensions on columns with the intersection showing existing relation.
For example
It would be great overview of models in the project from data relation perspective. It contains the similar information as ERD (suggested in #84) but visualized differently. It could be generated from FK tests/relations as the ERD
Few points that need to be decided:
what models do we show on rows and columns? all or filter them in config or let user filter them
do we want to separate facts on rows and dimensions on columns? how do we identify them then?
do we want all models on rows/columns? how to make the viz clean if there are hundreds of models?
Who will this benefit?
It would be useful to see relations between tables (for example what tables have reference to a Customer?). It is also more compact overview of ERD, so it easier to orientate for new people if they are exploring the models in the project.
The text was updated successfully, but these errors were encountered:
This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days.
Describe the feature
Kimball came with a matrix overview to map business processes and shared dimensions. There are multiple variants as dw matrix, information matrix but in relation with dbt models the most useful would be matrix of fact tables on rows and dimensions on columns with the intersection showing existing relation.
For example
It would be great overview of models in the project from data relation perspective. It contains the similar information as ERD (suggested in #84) but visualized differently. It could be generated from FK tests/relations as the ERD
Few points that need to be decided:
Who will this benefit?
It would be useful to see relations between tables (for example what tables have reference to a Customer?). It is also more compact overview of ERD, so it easier to orientate for new people if they are exploring the models in the project.
The text was updated successfully, but these errors were encountered: