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
consistently takes 4-5 minutes to compile the SQL.
Expected Behavior
I would expect SQL to be compiled in seconds, if not sub-seconds.
Steps To Reproduce
Define a large enough set of metrics and try compiling the SQL with --explain.
Use case
My current use case is to compile SQL for creating 3 x 6 tables on a combination of geographical (city, country, global) and time (hour, day, week, month, quarter, year) grains. Before you ask why I don't use the metrics dynamically, I want to stress, there are specific reporting purposes why we want to create those tables beforehand and not scan HUGE tables at query time. If I want to add, remove or update a metric in that SQL, this becomes 3 x 6 x 4 = 72 minutes!
Relevant log output
No response
Environment
- OS: mac os
- Python: 3.11
- dbt: 1.8 (core!)
- metricflow: 0.206.0
Which database are you using?
other (mention it in "Additional Context")
Additional Context
Database: Databricks
The text was updated successfully, but these errors were encountered:
Is this a new bug in metricflow?
Current Behavior
Saved query with ~80 metrics. Most of them derived metrics (ratios or averages).
consistently takes 4-5 minutes to compile the SQL.
Expected Behavior
I would expect SQL to be compiled in seconds, if not sub-seconds.
Steps To Reproduce
Define a large enough set of metrics and try compiling the SQL with
--explain
.Use case
My current use case is to compile SQL for creating 3 x 6 tables on a combination of geographical (city, country, global) and time (hour, day, week, month, quarter, year) grains. Before you ask why I don't use the metrics dynamically, I want to stress, there are specific reporting purposes why we want to create those tables beforehand and not scan HUGE tables at query time. If I want to add, remove or update a metric in that SQL, this becomes 3 x 6 x 4 = 72 minutes!
Relevant log output
No response
Environment
Which database are you using?
other (mention it in "Additional Context")
Additional Context
Database: Databricks
The text was updated successfully, but these errors were encountered: