[GitHub] [airflow] uranusjr commented on issue #26429: ExternalTaskSensor: An option to use the data_interval variables rather than execution_date

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

uranusjr commented on issue #26429:
URL: https://github.com/apache/airflow/issues/26429#issuecomment-1249055629

   Makes sense. I believe there’s some discussion somewhere, but this write up is more complete. I think we should allow using either `data_interval_start` _or_ `data_interval_end`; technically `data_interval_start` can be different from `execution_date`.
   
   To simplify implementation, perhaps it’s a good idea to split the logic into three sensors, one for each value? The three sensors would inherit from the same class that implements most of the logic, but inherited to applied on different values.


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