-
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
DEPRECATE(sdk): DSL - Deprecated output_artifact_paths parameter in ContainerOp constructor #2334
Conversation
/retest |
6 similar comments
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
@Ark-kun does this need to get merged? |
… constructor The users should switch to file_outputs instead. Previously `file_outputs` only supported small data outputs, but now it supports big files.
f387c5a
to
fbf1967
Compare
f387c5a
to
fbf1967
Compare
…hs-parameter-in-ContainerOp-constructor
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Ark-kun 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 |
What do you think about the new title? I can add some configuration to make these PRs show up in a separate section in changelog. |
/lgtm leave to you to decide title |
/unhold |
@Ark-kun how does file outputs support big data passing? What happens if a downstream component refers to the output using inputValue? /cc @paveldournov |
Reverting most of the kubeflow#2334 which inadvernetnly broke those artifacts by causing the names to be mangled. KFP's DSL compiler prepends template names to output names to ensure global uniqueness of *input* names (DSL's ContainerOp does not have concept of inputs, so the inputs are generated during the compilation including input names). But prepending template names to the output names stops the backend from recognizing the mlpipeline-ui-metadata and mlpipeline-metrics artifacts.
Reverting most of the kubeflow#2334 which inadvertently broke those artifacts by causing the names to be mangled. KFP's DSL compiler prepends template names to output names to ensure global uniqueness of *input* names (DSL's ContainerOp does not have concept of inputs, so the inputs are generated during the compilation including input names). But prepending template names to the output names stops the backend from recognizing the mlpipeline-ui-metadata and mlpipeline-metrics artifacts.
Reverting most of the #2334 which inadvertently broke those artifacts by causing the names to be mangled. KFP's DSL compiler prepends template names to output names to ensure global uniqueness of *input* names (DSL's ContainerOp does not have concept of inputs, so the inputs are generated during the compilation including input names). But prepending template names to the output names stops the backend from recognizing the mlpipeline-ui-metadata and mlpipeline-metrics artifacts.
…ontainerOp constructor (kubeflow#2334) The users should switch to file_outputs instead. Previously `file_outputs` only supported small data outputs, but now it supports big files.
Reverting most of the kubeflow#2334 which inadvertently broke those artifacts by causing the names to be mangled. KFP's DSL compiler prepends template names to output names to ensure global uniqueness of *input* names (DSL's ContainerOp does not have concept of inputs, so the inputs are generated during the compilation including input names). But prepending template names to the output names stops the backend from recognizing the mlpipeline-ui-metadata and mlpipeline-metrics artifacts.
The users should switch to file_outputs instead.
Previously
file_outputs
only supported small data outputs, but now it supports big files.This change is