The measure property create_metric currently exists in protocol spec, the pydantic implementation, and even has a transformation rule CreateProxyMeasureRule which utilizes it. All of these are remnants of the pre MetricFlow x dbt core integration world. The truth is that create_metric is a parse time configuration and not a query time configuration. It shouldn't exist in the protocols because create_metric is not a semantic layer concern.
Acceptance criteria
create_metric removed from jsonschema
create_metric removed from protocol spec
create_metric removed from pydantic implementation
CreateProxyMeasureRule deleted
Impact to Other Teams
This work impacts the Semantic Layer Team, Cloud Artifacts Team, and Core Team at dbt Labs.
Housekeeping
Short description
The measure property
create_metriccurrently exists in protocol spec, the pydantic implementation, and even has a transformation ruleCreateProxyMeasureRulewhich utilizes it. All of these are remnants of the pre MetricFlow x dbt core integration world. The truth is thatcreate_metricis a parse time configuration and not a query time configuration. It shouldn't exist in the protocols becausecreate_metricis not a semantic layer concern.Acceptance criteria
create_metricremoved from jsonschemacreate_metricremoved from protocol speccreate_metricremoved from pydantic implementationCreateProxyMeasureRuledeletedImpact to Other Teams
This work impacts the Semantic Layer Team, Cloud Artifacts Team, and Core Team at dbt Labs.
Will backports be required?
No
Context
No response
SL-1603