-
Notifications
You must be signed in to change notification settings - Fork 148
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
Populating Pipeline/Workspace field in kubeflow artifacts #138
Comments
Hi, I am not very clear about the context here as you mentioned "earlier package", could you be more specific on that? Ideally, if the pipeline/workspace is a field of a artifact, we will be able to group it using the MLMD Declarative Nodes Filtering. |
Hi, thanks for replying, github.com/kubeflow/metadata/blob/master/sdk/python/sample/demo.ipynb Here in cell3, we can define a workspace and for every pipeline run, all the artifacts will be saved in this workspace. |
Hi @abhaychand147, sorry for the late reply(I must have miss it). Unfortunately, the Back to your question, there are two options: 1. use each database as a workspace. 2. store the workspace value in one of the artifact's property and use MLMD Declarative Nodes Filtering to group them. |
In earlier package for saving metadata we were able to group artifacts based on a workspace, is it now possible with MLMD?
The text was updated successfully, but these errors were encountered: