This is an automated email from the ASF dual-hosted git repository.
uranusjr pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new ce48567c54 Add note on subtle logical date change in 2.2.0 (#24413)
ce48567c54 is described below
commit ce48567c54d0124840062b6bd86c2a745d3cc6d0
Author: Tzu-ping Chung <[email protected]>
AuthorDate: Mon Jun 13 22:42:24 2022 +0800
Add note on subtle logical date change in 2.2.0 (#24413)
---
RELEASE_NOTES.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/RELEASE_NOTES.rst b/RELEASE_NOTES.rst
index 66edcf9c90..33cae19c5c 100644
--- a/RELEASE_NOTES.rst
+++ b/RELEASE_NOTES.rst
@@ -1244,6 +1244,13 @@ DaskExecutor - Dask Worker Resources and queues
If dask workers are not started with complementary resources to match the
specified queues, it will now result in an ``AirflowException``\ , whereas
before it would have just ignored the ``queue`` argument.
+Logical date of a DAG run triggered from the web UI now have its sub-second
component set to zero
+"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
+Due to a change in how the logical date (``execution_date``) is generated for
a manual DAG run, a manual DAG run’s logical date may not match its
time-of-trigger, but have its sub-second part zero-ed out. For example, a DAG
run triggered on ``2021-10-11T12:34:56.78901`` would have its logical date set
to ``2021-10-11T12:34:56.00000``.
+
+This may affect some logic that expects on this quirk to detect whether a run
is triggered manually or not. Note that ``dag_run.run_type`` is a more
authoritative value for this purpose. Also, if you need this distinction
between automated and manually-triggered rus for “next execution date”
calculation, please also consider using the new data interval variables
instead, which provide a more consistent behavior between the two run types.
+
New Features
^^^^^^^^^^^^
