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

Support branch/condition component #498

Closed
zhitaoli opened this issue Aug 16, 2019 · 4 comments
Closed

Support branch/condition component #498

zhitaoli opened this issue Aug 16, 2019 · 4 comments
Assignees

Comments

@zhitaoli
Copy link
Contributor

The current data aware TFX pipeline and component does not support conditional execution or branching (consider the PythonBranchOperator in Airflow or Argo's conditional). We should provide some support here.

@ruoyu90 @krazyhaas

@robertlugg
Copy link
Contributor

robertlugg commented Sep 17, 2019

Hi @zhitaoli, it is possible to filter data based on some criteria. This criteria usually is defined in terms of your data. But, it wouldn't have to be. You could just create a component with a parameter "switch" that makes your decision. This component could output all the data, some of the data, none of the data, or even output some data in one output channel and the other data in a different output channel. Would this type of strategy work for your use case?

@ConverJens
Copy link
Contributor

@zhitaoli Is there an update to this? My main motivation would be to enable/disable Tuner based on a RuntimeParameter in KubeFlow.

@zhitaoli
Copy link
Contributor Author

@kennethyang404 and @ruoyu90 will work on this. Can you confirm whether branching based on value of a RuntimeParameter is part of the design scope?

@lego0901
Copy link
Member

Sorry for the very late response, but this looks viable through tfx.v1.dsl.Cond. Thanks!

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

6 participants