You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 4, 2024. It is now read-only.
Currently the launch operator defaults to 'all_success' and it doesn't appear to have an option to pass trigger_rule's to this operator. Thus when any task upstream is skipped, the launch task skips and linked tasks fail, despite differing trigger_rule's applied to the DatabricksNotebookOperator's.
Is it possible to pass trigger_rule's to this Operator, and if not can this functionality be added?
The text was updated successfully, but these errors were encountered:
leungadrian
changed the title
'launch' Operator trigger_rule Option
Launch Operator trigger_rule Option
Jan 17, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently the launch operator defaults to 'all_success' and it doesn't appear to have an option to pass trigger_rule's to this operator. Thus when any task upstream is skipped, the launch task skips and linked tasks fail, despite differing trigger_rule's applied to the DatabricksNotebookOperator's.
Is it possible to pass trigger_rule's to this Operator, and if not can this functionality be added?
The text was updated successfully, but these errors were encountered: