[CT-2520] [Epic] dbt-core 1.6 x MetricFlow Integration

[QMalcolm]

For 1.6 our plan is to have a basic integration of MetricFlow with dbt-core for the semantic layer. What this integration looks like for dbt-core 1.6 is the following

• people will be able to define semantic layer objects in YAML files as defined in New dbt Semantic Layer Spec Proposal #7456
• core will parse these objects to the manifest as nodes
• core will output a new semantic manifest artifact
• adapters will allow for the optional installation of MetricFlow (i.e. $ pip install dbt-snowflake[metricflow]) (i.e. $ pip install "dbt-metricflow[snowfalke]")
• querying will happen via the MetricFlow CLI for 1.6 (e.g. $ mf query <metric_name> ...

[P0] End-to-end

Preview Give feedback

1. [CT-2496] [Spike] Determine best practices for composing nodes with python Protocols #7470
   MetricFlow Team:Language spike +3
   
2. [CT-2521] Define SemanticModel node for the Manifest #7499
   MetricFlow Team:Language +2
   
3. [CT-2522] Redefine Metric node for the Manifest and update parsing #7500
   MetricFlow Team:Language +2
   
4. [CT-2523] Begin parsing of Metrics to the Manifest as nodes #7501
   MetricFlow Team:Language +2
5. [CT-2525] Begin "basic" parsing of SemanticModel to the Manifest as nodes #7503
   MetricFlow Team:Language +2
   
6. [CT-2434] [Feature] Create SemanticManifest artifact with every run #7404
   MetricFlow Team:Language enhancement metrics semantic +5
   

[P0/1] Follow-ups from end-to-end

Preview Give feedback

1. [SPIKE] [CT-2651] Add SemanticModels and Metrics to the DAG #7800
   MetricFlow spike +2
   
2. [CT-2666] Review Test Coverage of SemanticModels #7820
   semantic +1
   
3. [CT-2667] Review Test Coverage of New Metrics #7821
   semantic +1
   
4. [CT-2668] Improve ref() Parsing for SemanticModel Objects #7822
   MetricFlow +1
   
5. [SPIKE] [CT-2669] Revisit NodeRelation #7823
   MetricFlow spike +2
   
6. [CT-2671] Check Semantic Interface Protocol Implementations in Core #7827
   MetricFlow +1
   
7. [CT-2677] [BUG] Update SemanticModel definitions to match DSI 0.1.0dev3 protocols #7833
   MetricFlow bug +2
   
8. [CT-2690] Update DSI version to 0.1.0dev5 #7853
   semantic +1
   
9. [CT-2696] Compilation error when rendering filter in metrics #7864
   bug semantic +2
   
10. [CT-2697] Can't use integers in measure expr #7865
    bug semantic +2
    
11. [CT-2698] use_approximate_percentile and use_discrete_percentile keys defualt to None but are defined as bool in the protocol #7866
    bug semantic +2
    
12. [CT-2707] Derived metrics throw an error when using the run based semantic manifest. #7884
    bug semantic +2
    
13. [CT-2711] Ensure full partial parsing capability for Semantic Models #7897
    semantic +1
    
14. [CT-2712] Update DSI Version to 0.1.0dev7 #7898
    semantic +1
    
15. [CT-2719] Rename manifest key: semantic_nodes -> semantic_models #7907
    artifacts semantic tech_debt +3
    
16. [CT-2734] Add metricflow_time_spine to the semantic manifest. #7938
    enhancement semantic +2
    
17. [CT-2691] Populate MetricNode depends_on #7854
    semantic +1
    
18. [CT-2752] Run DSI SemanticManifest validations during parsing #7969
    enhancement semantic +2
    
19. [CT-2812] Remove create_metric property from end user facing Measure spec #8064
    semantic +1
20. [CT-2813] Begin compiling filter attrs on Metric nodes #8065
    semantic +1
    
21. [CT-2818] Anonymous usage tracking for semantic object definitions #8077
    semantic +1
    

[P0] Migration support

Preview Give feedback

1. [CT-2529] Migration tool for moving from dbt-metrics to new semantic layer specs #7507
   semantic +1
   

[P1] Adapters

Preview Give feedback

1. [CT-2681] [Feature] Add explain or dry_run method to BaseAdapter #7839
   4 of 4
   MetricFlow Team:Adapters enhancement +3
   

[jtcohen6]

I opened a new epic for tracking the next milestone of work:

• [CT-2831] [Epic] dbt-core 1.7 <> Semantic Layer #8125