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

Set mark_end_on_close after set_context #35761

Merged

Conversation

dstandish
Copy link
Contributor

In ES task handler, set_context applies its own logic for mark_end_on_close, so it we must set the attr after for our override to persist.

In ES task handler, set_context applies its own logic for mark_end_on_close, so it we must set the attr after for our override to persist.
@dstandish dstandish force-pushed the set-end-marker-behavior-after-set-context branch from 9565326 to 528883b Compare November 20, 2023 21:23
@dstandish dstandish merged commit 7389782 into apache:main Nov 21, 2023
47 checks passed
@dstandish dstandish deleted the set-end-marker-behavior-after-set-context branch November 21, 2023 13:42
@dstandish dstandish added this to the Airflow 2.8.0 milestone Nov 22, 2023
@ephraimbuddy ephraimbuddy added the type:improvement Changelog: Improvements label Nov 23, 2023
ephraimbuddy pushed a commit that referenced this pull request Nov 23, 2023
In ES task handler, set_context applies its own logic for mark_end_on_close, so it we must set the attr after for our override to persist.
ephraimbuddy pushed a commit that referenced this pull request Nov 26, 2023
In ES task handler, set_context applies its own logic for mark_end_on_close, so it we must set the attr after for our override to persist.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:logging type:improvement Changelog: Improvements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants