Determine fail_stop on client side when db isolated #39258
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dstandish
requested review from
kaxil,
ashb,
bolkedebruin and
XD-DENG
as code owners
potiuk
approved these changes
Apr 25, 2024
vincbeck
approved these changes
Apr 25, 2024
dirrao
approved these changes
Apr 26, 2024
This is needed because we do not ser the dag on Operator objects.
dstandish
force-pushed
the
determine-fail_stop-on-client-side-when-db-isolated
branch
from
98343ee
to
9cfe9a5
Compare
Taragolis
approved these changes
Apr 28, 2024
RodrigoGanancia
pushed a commit
to RodrigoGanancia/airflow
that referenced
this pull request
May 10, 2024
* Determine fail_stop on client side when db isolated This is needed because we do not ser the dag on Operator objects. * fix tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is needed because we do not ser the dag on Operator objects.