-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Artifact type based visualization for HTML, Markdown and etc #3970
Comments
Thanks @Ark-kun for preparing the sample for me! That's super helpful. I'll put this into post 1.0 planning for now. I think it's low effort and really beneficial, definitely something I want to do. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
/lifecycle frozen |
Moving this to KFP IR backlog, it should work with MLMD artifacts. |
Code example for downloading artifact content: pipelines/frontend/src/components/MinioArtifactPreview.tsx Lines 137 to 142 in f3c0c46
|
Previously I've started exploring solution for this in: https://github.com/Ark-kun/pipelines/commits/Frontend---Visualize-HTML It does not do anything yet. Just getting component spec for a node, so that we can get to the output types. |
Currently we cannot get visualization type from Artifact type in V2 compatible: UI rely on type to visualize viewerContent: https://github.com/kubeflow/pipelines/blob/master/frontend/src/lib/OutputArtifactLoader.ts#L84. But we cannot get this information on V2 compatible. There are a few potential options:
We need some help to make this decision for exposing original artifact type to UI. |
Currently pending the decision and implementation of #5798. |
(#6349) * test: Update visualization v2 to output HTML and Markdown. * address comment * vis test
Currently, the UX visualizes data from
mlpipleine-ui-metadata
output JSON structure.It would be great to just support visualizing the individual output artifacts based on type. Only few simple types are needed: HTML and Markdown (plus maybe URI). Everything more complicated can be accomplished by visualizer components.
This issue is a prerequisite for visualizer components.
Example code that generates several typed outputs:
After the execution has finished here are the pod annotations ().
To get the types we should probably join
workflows.argoproj.io/outputs
withpipelines.kubeflow.org/component_spec
. We can take the Argo outputs, remove the common template name prefix (create-visualizations-
) from output names, then normalize and match them with thecomponent_spec
outputs.The text was updated successfully, but these errors were encountered: