[GitHub] [airflow] mjpieters commented on issue #11893: Smart sensor contexts appear confusing, redundant and incomplete

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

mjpieters commented on issue #11893:
URL: https://github.com/apache/airflow/issues/11893#issuecomment-719108383


   I am using the TI primarily to access the `execution_date` and `dag_id` values. 
   
   I was also using it as a gateway to fetch XCom values, but I'm pretty sure that in my sensors this can and should actually be done in `pre_execute` instead (fetching the value just once then storing the information in the context instead of retrieving the value on the each poke).
   
   Note that I am perfectly prepared to accept that to be smart-sensor compatible the implementation may have to put up with a limited subset of functionality. As long as the common scalar values such as `execution_date` are present and for the common cases we don't have to differentiate between regular and smart-sensor modes when implementing the `poke` method I think a shim TI object would be fine.


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

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