Skip to content

Support inputs with multiple arguments #1933

Description

@Ark-kun

Need to support variadic inputs in ComponentSpec, Lightweight components, load_component etc.

In command-line we can pass multiple inputs as repeated command-line parameters: --a 1 --a 2.
In TaskSpec we can make argument a list: arguments: {a: [1, 2]}.
In inputSpec we could add repeated: true or allowMultiple: true property.
In ContainerImplementation we could specify the command args as follows: {map: {source: {inputValue: RepInput}, selector: [--a, {item}] }}

Related: #1901

Activity

  1. self-assigned this
    on Aug 22, 2019
  2. areshytko commented on Apr 7, 2020

    @areshytko

    is this feature planned to be implemented in the upcoming releases? It would be great to have it in KFP

  3. Ark-kun commented on Apr 10, 2020

    @Ark-kun
    ContributorAuthor

    is this feature planned to be implemented in the upcoming releases? It would be great to have it in KFP

    At this moment there we have no bandwidth for implementing this feature. It needs many places to change.

    What is the scenario where you might want this feature?

  4. areshytko commented on Apr 10, 2020

    @areshytko

    The use case is the following: we have K-fold a cross-validation task somewhere in the middle of our pipelines, and the number of fold is the parameter to the pipeline. The desire is to distribute computation of each fold to a separate task and run them in parallel since this is a time-consuming operation. Basically this requires the following:

    image
    Task C now requires a variable number of input parameters.

    Can we offer our help and contribute to the implementation of this feature under this ticket?

  5. ca-scribner commented on Jun 16, 2020

    @ca-scribner
    Contributor

    Does anyone have a pattern to make something like this work? The only hacks I've thought of would be maybe something like a simple shell call that takes the values from TaskB-1...TaskB-N and concatenates them to a single string (json or just space deliminated) or maybe to lines in a file, then TaskC takes that concatenation as input and knows how to parse it

    Other ideas might be that TaskB-* concatenate their results somewhere central and TaskC grabs from there. So maybe TaskB-* write results to the same location, and TaskC grep's from there?

  6. stale commented on Sep 15, 2020

    @stale

    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.

  7. added
    lifecycle/staleThe issue / pull request is stale, any activities remove this label.
    on Sep 15, 2020
  8. stale commented on Sep 22, 2020

    @stale

    This issue has been automatically closed because it has not had recent activity. Please comment "/reopen" to reopen it.

  9. removed
    lifecycle/staleThe issue / pull request is stale, any activities remove this label.
    on Sep 22, 2020
  10. removed
    lifecycle/staleThe issue / pull request is stale, any activities remove this label.
    on Sep 22, 2020
  11. BenoitLeguay commented on Aug 17, 2021

    @BenoitLeguay

    Any news on this feature ? :)
    Thank you !

  12. SaschaHeyer commented on Feb 23, 2022

    @SaschaHeyer

    This feature request is closely related to #3412
    Are there any updates on that this is a request I have seen already multiple times.

  13. rimolive commented on Apr 5, 2024

    @rimolive
    Member

    Closing this issue. No activity for more than a year.

    /close

  14. google-oss-prow commented on Apr 5, 2024

    @google-oss-prow

    @rimolive: Closing this issue.

    Details

    In response to this:

    Closing this issue. No activity for more than a year.

    /close

    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.

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

Metadata

Metadata

Assignees

Type

No type

Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions