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

Correct metadata inaccuracy in the output viewer docs #2214

Merged
merged 2 commits into from Sep 28, 2020

Conversation

lucinvitae
Copy link
Contributor

This corrects a misleading sentence in the output viewer documentation, where the docs suggest the file name matters, but in reality the artifact name is what matters.

This recreates #2212 which is experiencing a CI failure that may or may not be an unrelated race condition.

This corrects a misleading sentence in the output viewer documentation, where the docs suggest the file name matters, but in reality the artifact name is what matters.
@k8s-ci-robot
Copy link
Contributor

Hi @lucinvitae. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kubeflow-bot
Copy link

This change is Reviewable

@alfsuse
Copy link
Contributor

alfsuse commented Sep 25, 2020

/assign alfsuse

@alfsuse
Copy link
Contributor

alfsuse commented Sep 25, 2020

/lgtm

or else the Kubeflow Pipelines UI will not render the visualization. In other words,
the `.outputs.artifacts` setting for the generated pipeline component should show:
`- {name: mlpipeline-ui-metadata, path: /mlpipeline-ui-metadata.json}`.
The JSON filepath does not matter, although `/mlpipeline-ui-metadata.json`
Copy link
Contributor

Choose a reason for hiding this comment

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

LGTM @lucinvitae thank you.

If you have time, maybe you can reorder the words, so they can wrap at the 80 limit. For example:

The pipeline component must write a JSON file specifying metadata for the output
viewer(s) that you want to use for visualizing the results. The component must
also export a file output artifact with an artifact name of
`mlpipeline-ui-metadata`, or else the Kubeflow Pipelines UI will not render the
visualization. In other words, the `.outputs.artifacts` setting for the
generated pipeline component should show: `- {name: mlpipeline-ui-metadata,
path: /mlpipeline-ui-metadata.json}`. The JSON filepath does not matter,
although `/mlpipeline-ui-metadata.json` is used for consistency in the examples
below.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done!

@8bitmp3
Copy link
Contributor

8bitmp3 commented Sep 25, 2020

I think the /docs/pipelines approvers (OWNERS) are:
/assign @Bobgy @IronPan @neuromage @Ark-kun @numerology

We should create a new OWNERS for /docs/pipelines/sdk cc @alfsuse @RFMVasconcelos

alfsuse added a commit to alfsuse/website that referenced this pull request Sep 28, 2020
Hi all adding an OWNERS file to the SDK section as suggested by @8bitmp3  in kubeflow#2214
Currently proposing as approvers:
  - Bobgy
  - IronPan
  - neuromage
  - Ark-kun
  - numerology
I can add myself as a reviewer but would prefer someone else with more knowledge on the sdk than me.
@k8s-ci-robot k8s-ci-robot removed the lgtm label Sep 28, 2020
@numerology
Copy link

/lgtm
/approve

Thanks! @lucinvitae

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: numerology

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit ea56c11 into kubeflow:master Sep 28, 2020
k8s-ci-robot pushed a commit that referenced this pull request Sep 29, 2020
* Create OWNERS file for sdk section

Hi all adding an OWNERS file to the SDK section as suggested by @8bitmp3  in #2214
Currently proposing as approvers:
  - Bobgy
  - IronPan
  - neuromage
  - Ark-kun
  - numerology
I can add myself as a reviewer but would prefer someone else with more knowledge on the sdk than me.

* Update OWNERS.md

Updated reviewers with 8bitmp3 and @RFMVasconcelos.
I think we should be good now.

* Updated OWNERS.md

Removed users and fixed a typo
@yzhangswingman
Copy link

Hi there, ComponentSpec doc states that fileOutputs is a legacy property and should be avoided for forward compatibility. That leaves me confused about where to write the metadata json. If the json path does not matter, can I just write to the placeholder { outputPath: mlpipeline-ui-metadata }? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet