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

Populating Pipeline/Workspace field in kubeflow artifacts #138

Open
abhaychand147 opened this issue Jan 4, 2022 · 3 comments
Open

Populating Pipeline/Workspace field in kubeflow artifacts #138

abhaychand147 opened this issue Jan 4, 2022 · 3 comments

Comments

@abhaychand147
Copy link

abhaychand147 commented Jan 4, 2022

In earlier package for saving metadata we were able to group artifacts based on a workspace, is it now possible with MLMD?

@BrianSong
Copy link
Collaborator

BrianSong commented Jan 10, 2022

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.

@abhaychand147
Copy link
Author

abhaychand147 commented Jan 13, 2022

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.
The same can be seen in kubeflow UI under artifacts section.
Do we have the same grouping option available in mlmd?

@BrianSong
Copy link
Collaborator

BrianSong commented Mar 8, 2022

Hi @abhaychand147, sorry for the late reply(I must have miss it). Unfortunately, the Workspace is not a concept in MLMD, it should be an upstream concept that designed by KFP.

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.

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

No branches or pull requests

2 participants