[GitHub] [airflow] Chaho12 commented on issue #20797: Python Operator should pass keyword arguments to callbacks for sake of convenience

[GitBox <gi...@apache.org>]

Chaho12 commented on issue #20797:
URL: https://github.com/apache/airflow/issues/20797#issuecomment-1010588028


   Thank you for your reply. Can you recommend any books/references that I could start to learn more about the architecture ? I did some quick google search and found "The Complete Guide to Apache Airflow 2021", "Data Pipelines with Apache Airflow"
   
   When you say `forcefully (via UI) set to "success" state, the callbacks will be executed in the DagProcessor/Scheduler`, is this the case where the operator has started (state is at running, scheduled etc) and user forcefully changes state via UI?
   I've tried changing the state from `no_status` to  `success` (while it was waiting for other task to finish) and on_success_callback did not seem to be called.
   - Does defining my callable function within the same py file and calling another callable method at different py file have any effects to such case?


-- 
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: commits-unsubscribe@airflow.apache.org

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