ashb opened a new pull request, #73917: URL: https://github.com/apache/airflow/pull/73917
Coordinate TI keys can identify a replacement attempt after task coordinates are reused. Celery, Kubernetes, ECS, Batch and Lambda now retain the submitted UUID through dispatch, adoption, result handling and cleanup when airflow core exposes UUID executor support. Provider releases must still work with their declared older Airflow versions, so retain coordinate keys when that core capability is absent. Existing Celery and AWS jobs retain their external transport identifiers. Kubernetes recovers pre-upgrade pod UUIDs from the original workload and annotates adopted pods; it never resolves a late event through the current task at those coordinates. Lambda validates both UUID and legacy serialized transport keys before binding an adopted result to its attempt. --- <sub>Stack created with <a href="https://github.com/github/gh-stack";>GitHub Stacks CLI</a> • <a href="https://gh.io/stacks-feedback";>Give Feedback 💬</a></sub> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
