-
Notifications
You must be signed in to change notification settings - Fork 431
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
Dynamic (templated) names for model versions #2909
Dynamic (templated) names for model versions #2909
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add Documentation and Community
|
@coderabbitai review |
Actions performedReview triggered.
|
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.
I tried to review this but I feel I lack the understanding how the whole model linkage to pipeline/step runs is supposed to work. @avishniakov can you maybe explain that before I continue?
- I can configure a pipeline/step to be associated with a certain model by putting it in the decorator/config file
- These will be linked to my pipeline run/step run
- Are there other ways that we link models and pipeline/step runs?
You nailed it! If you put it in one of the decos - it will be associated with the corresponding run (and also linked to a pipeline run - this is still a separate entity). With these changes, theoretically, it should be possible to sunset the pipeline run model version links table (to be validated and realigned with the model). If you put model definitions elsewhere, e.g. in step codes - no link will be created. This is by design as of now. Subject to change though, while it might make sense not only to track the links, but also to keep track of link flavor (read, write, own, etc.). |
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.
Adding a few more comments on top of Michael's review.
src/zenml/integrations/gcp/orchestrators/vertex_orchestrator.py
Outdated
Show resolved
Hide resolved
CI is not progressing much now, but can you re-review please? |
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.
Nice, it already seems much less complex now! Just left a few more small suggestions but for the most part looks good
Describe changes
This PR gives the ability to name Model Versions using
{date}
and{time}
placeholders to use for automated runs with meaningful naming or for scheduling purposes.Model(version="my_model_version_{date}_{time}",...)
will be translated into a meaningful name upon pipeline execution.This PR also has some minor improvements/refactors to ensure that the Model Version is created at a proper time and uses the time of the run as a filler.
Results of testing in Pro:
Pre-requisites
Please ensure you have done the following:
develop
and the open PR is targetingdevelop
. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.Types of changes