eladkal closed issue #35415: Wrong execution date in SLA alerts
URL: https://github.com/apache/airflow/issues/35415
--
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
hliu-VoleonGroup commented on issue #35415:
URL: https://github.com/apache/airflow/issues/35415#issuecomment-1845958983
@pateash Thanks for the reply.
To my understanding, `logicalDate` is a new concept in Airflow 2 and it is
equivalent to `executionDate`. Please correct me if I am
pateash commented on issue #35415:
URL: https://github.com/apache/airflow/issues/35415#issuecomment-1824923428
hi @hliu-VoleonGroup
this logicalDate represents(logical date of next dagrun) or the Data
interval end time ( when SLA was fired ).
boring-cyborg[bot] commented on issue #35415:
URL: https://github.com/apache/airflow/issues/35415#issuecomment-1792890330
Thanks for opening your first issue here! Be sure to follow the issue
template! If you are willing to raise PR to address this issue please do so, no
need to wait for
hliu-VoleonGroup opened a new issue, #35415:
URL: https://github.com/apache/airflow/issues/35415
### Apache Airflow version
main (development)
### What happened
- The execution date in a triggered SLA alert is one schedule interval ahead
of the expected one.
-
