-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
Use the backend-configured model #12336
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make sense to be. Should we add some test around this?
Not sure how much that would achieve, tbh. The change just makes sure to use the same API the Celery db backend uses, and the existing tests already cover this area. Testing that |
The PR needs to run all tests because it modifies core of Airflow! Please rebase it to latest master or ask committer to re-run it! |
Rather than import the backend Task model directly, use the class that the backend actually uses. This could have been customised, and there is no reason not to use this reference.
aeff66f
to
6866f7e
Compare
…xist closes apache#14586 We add this feature in apache#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs
closes #14586 We add this feature in #12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs
closes #14586 We add this feature in #12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs (cherry picked from commit 33910d6)
closes #14586 We add this feature in #12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs (cherry picked from commit 33910d6)
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs (cherry picked from commit 33910d6c699b5528db4be40d31199626dafed912) GitOrigin-RevId: 5b3ce3ff11e0b6d5d63b10b5b7a3364399c1ed6e
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
closes apache/airflow#14586 We add this feature in apache/airflow#12336 but looks like for some users this attribute does not exist. I am not sure if they are using a different Celery DB Backend or not but even Celery > 5 contains this attribute (https://github.com/celery/celery/blob/v5.0.5/celery/backends/database/__init__.py#L66) and even Celery 4 but this commits use the Celery Task model when an attribute error occurs GitOrigin-RevId: 33910d6c699b5528db4be40d31199626dafed912
Rather than import the backend Task model directly, use the class that the backend actually uses. This could have been customised, and there is no reason not to use this reference.
Fixes #12138