[GitHub] [airflow] shubham22 commented on issue #31819: Improve the docs around deferrable mode for Sensors

["shubham22 (via GitHub)" <gi...@apache.org>]

shubham22 commented on issue #31819:
URL: https://github.com/apache/airflow/issues/31819#issuecomment-1585419556

   I agree that we need additional documentation to clarify the differences between sensors in various modes, particularly when the sensor is deferrable.
   
   > the deferrable = True in sensors is merely a convention used in a few of them. 
   
   Exactly! It isn't a convention and we shouldn't treat it as such, because it can be difficult to enforce. However, we could improve our documentation with general statements, such as distinguishing between a `deferrable sensor` and a `non-deferrable sensor`.
   
   > One could argue that there is really no need for a "deferrable" sensor because technically it could be a regular operator with deferrable method
   
   This was my line of thinking when prioritizing deferrable tasks for Amazon provider. If both an operator and sensor exist (like RedshiftCreateCluster), we are choosing to develop only a deferrable operator for now; if only a sensor exists (like S3KeySensor), the we add deferrable support to it. However, I have observed differing approaches from other providers who are prioritizing deferrable sensors over operators.


-- 
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