-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expose measures for metrics on MFEngine #735
Conversation
Thank you for your pull request! We could not find a changelog entry for this change. For details on how to document a change, see the contributing guide. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart from the typechecker override this all seems reasonable. I think it'll be more expedient to keep the change at the level of the engine and use the existing semantic_model_lookup methods to populate the additional fields you need.
Would you mind also updating the PR description with a little more context on why this change is being made? I'm assuming it's to support metadata lookups on the cloud side, but it's not clear to me how we're expecting this method to be used from the PR itself.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for your patience!
Resolves #SL-814
Description
Expose measures for metrics on MFEngine, ensuring that
agg_time_dimension
is populated even when it is inherited from the semantic model default.We need to know the agg_time_dimension for a given measure so that the API can expose a list of all measures and the name of their
agg_time_dimension
for a given metric. This allows users to understand whatmetric_time
actually represents for a given metric.