Set task name for 2.11.X path#63746
Conversation
fixes apache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.
|
CI image builds are broken in main |
|
Thanks for catching this @o-nikolas @Aakcht and for the quick fix in #63746. You're right — my fix in #63110 correctly registered The fix in #63746 looks correct — setting the explicit task name on the legacy module-level app ensures Airflow 2.x workers receive the short name they look for. Happy to help test or review if needed. |
Thanks for the review @kalluripradeep! If it looks good to you, please approve the PR 🙂 Also any testing is always welcomed, especially with this type of edge case. I tests manually but please double check my work |
Aakcht
left a comment
There was a problem hiding this comment.
Hi, tested it, the fix seems to help, thanks!
Cooool Thanks ! |
|
Failure unrelated - fixing it in #63763 |
|
Needs rebase I think |
After pulling in main the tests are green. Merging! |
|
cool |
fixes apache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.
fixes apache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.
fixes apache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.
fixes apache#63729 Celery now uses explicit task names when submitting tasks to workers, make sure to set that explicit name on the older module level app that Airflow 2.x uses.
fixes #63729
Celery now uses explicit task names when submitting tasks to workers (see
send_workload_to_executor), make sure to set that explicit name on the older module level app that Airflow 2.x uses.Was generative AI tooling used to co-author this PR?
claude
{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.