Skip to content
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

[Runs] Store artifact URIs instead of full artifacts in body [1.6.x] #5544

Merged
merged 16 commits into from May 12, 2024

Conversation

alonmr
Copy link
Member

@alonmr alonmr commented May 9, 2024

https://iguazio.atlassian.net/browse/ML-6397

Artifacts stats and preview can bloat the DB when stored in run body.
Instead we now only store the artifact URIs while in memory the run object still holds the artifacts (client side) to maintain easy access.

In the API we strip the artifacts if given and enrich the artifact URIs when storing / updating the runs.

Example from run yaml:
Screenshot 2024-05-12 at 18 27 17

Example from run output html:
Screenshot 2024-05-12 at 18 28 45

Copy link
Member

@theSaarco theSaarco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good - one small change needed.

mlrun/model.py Outdated
@@ -1058,6 +1058,7 @@ def __init__(
ui_url=None,
reason: str = None,
notifications: Dict[str, Notification] = None,
artifact_uris: list[str] = None,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs to be a dict now, doesn't it?

Copy link
Member

@theSaarco theSaarco left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cool. Looks good.

@alonmr alonmr merged commit a54892f into mlrun:1.6.x May 12, 2024
10 checks passed
@alonmr alonmr deleted the ML-6397 branch May 12, 2024 16:17
alonmr added a commit to alonmr/mlrun that referenced this pull request May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants