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

How to pass airflow task configuration to one custom component? #6438

Closed
Natielle opened this issue Nov 13, 2023 · 3 comments
Closed

How to pass airflow task configuration to one custom component? #6438

Natielle opened this issue Nov 13, 2023 · 3 comments

Comments

@Natielle
Copy link

System information

  • TFX Version (you are using): 0.22.0
  • Environment in which you plan to use the feature (e.g., Local
    (Linux/MacOS/Windows), Interactive Notebook, Google Cloud, etc..): Linux/Mac
  • Are you willing to contribute it (Yes/No): Yes

Describe the feature and the current behavior/state.
I would like to use the trigger_rule Airflow configuration in only one component. I know it is possible for all components from pipeline using the parameter airflow_dag_config (from this object AirflowPipelineConfig).
Is it possible to use trigger_rule configuration only to one component?
My component execution should be optional. This component is used to send updates to another system, if this optional component fails, it will not be able to interrupt the execution of the main tasks.

@singhniraj08 singhniraj08 self-assigned this Nov 15, 2023
@singhniraj08
Copy link
Contributor

@Natielle,

I don't think we have an option to add "trigger_rule" Airflow configuration in only one TFX component. Similar #498 feature request can help you use-case but it's still a work in progress. I would request you to close this issue and follow similar thread for updates on the feature implementation. Thank you!

Copy link
Contributor

This issue has been marked stale because it has no recent activity since 7 days. It will be closed if no further activity occurs. Thank you.

@github-actions github-actions bot added the stale label Nov 24, 2023
Copy link
Contributor

github-actions bot commented Dec 1, 2023

This issue was closed due to lack of activity after being marked stale for past 7 days.

@github-actions github-actions bot closed this as completed Dec 1, 2023
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

2 participants