[GitHub] [superset] 1c7 edited a comment on issue #18656: Question: `RESULTS_BACKEND` and `CELERY_RESULT_BACKEND` seem repeated? they look like the same thing but why there are two of them?

[GitBox]

1c7 edited a comment on issue #18656:
URL: https://github.com/apache/superset/issues/18656#issuecomment-1034626256


   # Celery Documentation
   
https://docs.celeryproject.org/en/stable/userguide/configuration.html#task-result-backend-settings
   
   
   Section Introduction
   <img width="1238" alt="image" 
src="https://user-images.githubusercontent.com/1804755/153367728-1029ae5a-85c1-4e52-ba2c-5d26873d5022.png";>
   
   <img width="1193" alt="image" 
src="https://user-images.githubusercontent.com/1804755/153367769-5da7f269-14e2-4f68-822a-e55f69dd7156.png";>
   
   <img width="1207" alt="image" 
src="https://user-images.githubusercontent.com/1804755/153367854-28f2d6fc-dd08-40a4-9bdf-94503b20ad6c.png";>
   
   # Conclusion: Celery does support `CELERY_RESULT_BACKEND`
   Because Celery Docs says:  
   
   > Celery will still be able to read old configuration files until Celery 6.0.
   
   Right now Superset are using Celery `5.2.3`
   So `CELERY_RESULT_BACKEND` still works in Celery 5.2.3


-- 
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: notifications-unsubscr...@superset.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org