forked from mlop-ai/mlop
-
Notifications
You must be signed in to change notification settings - Fork 2
feat(query): add get_raw_metrics for SDK access to un-deduped writes #105
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
Open
asaiacai
wants to merge
2
commits into
main
Choose a base branch
from
feat/query-raw-metrics-sdk
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Consider renaming the
logGroupcolumn tometricin the returned data for consistency withget_metrics. In the Pluto SDK,metricis the standard name for the metric identifier column. Additionally, usingresp.get('rows') or []is safer thanresp.get('rows', [])as it handles cases where the server might explicitly returnnullfor therowskey, preventing potential iteration errors.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.
Pushing back on both:
1.
logGroup→metricrename. Two different fields:logNameis the full metric identifier (train/loss) — that's whatget_metricsrenames tometric(see pluto/query.py:247-249).logGroupis the prefix only (trainfortrain/loss) — a separate, narrower field.Renaming
logGroup→metricwould put the prefix string into a column namedmetric, which is semantically wrong and would mislead callers. Also,metric_nameis required onget_raw_metricsso every row in a response is already for the same metric — there's no need for ametriccolumn to disambiguate (which is the actual reasonget_metricshas one: it can be called for many metrics at once and merges results).2.
resp.get('rows') or []. The server endpoint's Zod schema isrows: z.array(...)— non-null by contract. The current.get('rows', [])is already more defensive than peer methods in this file (e.g.get_metricsdoes bareresult['metrics']indexing at pluto/query.py:241/244). Addingor []would guard a state the response schema can't produce and would be inconsistent with the rest of the module.Not applying either.