Use start_date and end_date to calculate duration when duration is null for running taskinstance.#61898
Conversation
|
I think it looks like the CI failure might be unrelated to this PR. |
…ll for running taskinstance.
Backport failed to create: v3-1-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker edd97b4 v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continueIf you don't have cherry-picker installed, see the installation guide. |
…ration is null for running taskinstance (apache#61898) (cherry picked from commit edd97b4) Co-authored-by: Karthikeyan Singaravelan <tir.karthi@gmail.com>
|
Manual backport #62136 |
…ll for running taskinstance (apache#61898)
…ll for running taskinstance (apache#61898)
…ll for running taskinstance (apache#61898)
…ll for running taskinstance (apache#61898)
…ll for running taskinstance (apache#61898)
When the task instance is in running state the duration value is null in the database and response. For task instances in running state use start_date and current time since end_date is null for duration calculation.
Was generative AI tooling used to co-author this PR?
No