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
A bug was raised in MetricFlow recently (dbt-labs/metricflow#764) outlining how null values are not handled properly in some cases. The proposed solution (dbt-labs/metricflow#759) requires changes to the MetricInputMeasure protocol used by MetricTypeParams protocol on Metric protocol. Specifically two new optional properties need to be added
join_to_timespine which should have a boolean value
fill_nulls_with which should optionally have a integer value
In the pydantic object implementations
join_to_timespine should default to false if not specified during parsing / deserialization
fill_nulls_with should default to None if not specified during parsing / deserialization
The text was updated successfully, but these errors were encountered:
A bug was raised in MetricFlow recently (dbt-labs/metricflow#764) outlining how null values are not handled properly in some cases. The proposed solution (dbt-labs/metricflow#759) requires changes to the
MetricInputMeasure
protocol used byMetricTypeParams
protocol onMetric
protocol. Specifically two new optional properties need to be addedjoin_to_timespine
which should have a boolean valuefill_nulls_with
which should optionally have a integer valueIn the pydantic object implementations
join_to_timespine
should default to false if not specified during parsing / deserializationfill_nulls_with
should default to None if not specified during parsing / deserializationThe text was updated successfully, but these errors were encountered: