Remove unused span_status DB columns#69278
Merged
Merged
Conversation
xBis7
reviewed
Jul 3, 2026
2678783 to
99b2182
Compare
Contributor
|
It turns out that the sleep that was initially used for the span_status, now provides enough time for jaeger to pick up the spans. Removing it make the otel test flaky. |
99b2182 to
48eaa1b
Compare
48eaa1b to
c88a489
Compare
ashb
reviewed
Jul 7, 2026
df7ca86 to
94c6200
Compare
94c6200 to
783ffc2
Compare
783ffc2 to
22bd5b5
Compare
Contributor
Author
|
@ashb The version is updated, the merge conflicts are resolved, all the CI checks are passed. I think we can merge this now. Thank you. |
This file contains hidden or 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
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.
Description
This PR removes the
span_statuscolumn fromdag_run,task_instanceandtask_instance_historyand associatedSpanStatusenum. This field previously tracked OpenTelemetry span lifecycle state and is no longer needed after #62554.Changes
DagRun,TaskInstance, andTaskInstanceHistorymodelsWas generative AI tooling used to co-author this PR?
Co-authored by: [Claude Opus 4.8] following the guidelines
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.