v0.111.0

Metricflow 0.111.0 was released today!

The big news is we have added data source inference as a Beta feature. It allows new users to quickly get started with Metricflow by bootstrapping their data source configurations from a warehouse connection.

Please note that this is still Beta feature. As such, it should not be expected to be free of bugs, and its CLI/Python interfaces might change without prior notice.

For full details see our release notes.

[0.111.0] - 2022-08-10

Added

• Early beta for data source inference - Snowflake users can now run a command to bootstrap data source definitions based on warehouse metadata for tables in a given schema. Check out mf infer --help for more details. Feedback welcome! (@serramatutu)
• Support for semi-additive measures - semi-additive measures are measures which can be aggregated across some dimensions, but not others. The most common use case for this is an end-of-period measure, such as a statement balance or end of day inventory hold. As of this release we support semi-additive restrictions bound by any time dimension. See the description on PR #183 for more details on usage. (@WilliamDee)
• Expanded data warehouse validations - data warehoue validation runs will now check to ensure all measures, identifiers, and dimensions defined in data sources are queryable. (@QMalcolm)

Fixed

• Resolved serialization error on custom Pydantic objects in the model parser (@tlento)
• Cleaned up error message handling and missing test depencies on model validation (@tlento)
• Eliminated a class of circular import errors by forking reference classes from the specs module (@WilliamDee)
• Fixed error state when specifying a where constraint with metric_time (@plypaul)

Updated

• Updated the tutorial to use metric_time instead of arbitrary time dimensions (@plypaul)
• Increased strictness of typechecking enforcement (@tlento)
• Removed unnecessary "all time" WHERE clause rendering for cases where time constraints were not provided (@WilliamDee)
• Updated Click version from ^8.1.3 to >=7.1.2 to temporarily resolve dependency issue for downstream Flask 1.1.4 usage (@jack-transform)
• Updated Jinja2 version from 2.11.0 to >=2.11.0 to allow downstream Flask 1.1.4 users to update to 2.x.x (@jpreillymb, @tlento)