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

Replacement of components with "@graph_component" decorator in V2 #10748

Open
rimolive opened this issue Apr 24, 2024 Discussed in #10717 · 1 comment
Open

Replacement of components with "@graph_component" decorator in V2 #10748

rimolive opened this issue Apr 24, 2024 Discussed in #10717 · 1 comment

Comments

@rimolive
Copy link
Member

rimolive commented Apr 24, 2024

/area sdk
/kind feature

Discussed in #10717

Originally posted by cs-gennadiy April 21, 2024
Please advise or correct me in following Use Case:

With kfp V1:

  1. componentA: submits spark application by container with kubectl apply -f spark_app_manifest.yml to spark operator
  2. componentB (task inner to componentC): gets application state by kubectl get SparkApplication myApp ...
  3. componentC (with "@graph_component" decorator): creates and runs task from componentB. Checks application state - if it isn't equal to "COMPLETED", then runs itself recursively.

With kfp V2:

the "@graph_component" decorator doesn't exist, so there is no way to run a task recursively. A workaround would be to implement "get and check state" loop, like "while" loop, inside of the same component function or command (E.g. using of "dsl.If" wouldn't be possible then).

Is my assumption for V2 correct?

@rimolive
Copy link
Member Author

/area sdk
/kind feature

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

No branches or pull requests

1 participant