ashokraminedi commented on code in PR #72678:
URL: https://github.com/apache/airflow/pull/72678#discussion_r4147354791
##########
task-sdk/src/airflow/sdk/bases/operator.py:
##########
@@ -705,14 +705,7 @@ class derived from this one results in the creation of a
task object,
retry_exponential_backoff=5, retries occur after 4min, 20min, 100min,
etc.
:param max_retry_delay: maximum delay interval between retries, can be set
as
``timedelta`` or ``float`` seconds, which will be converted into
``timedelta``.
- :param start_date: The ``start_date`` for the task, determines
- the ``logical_date`` for the first task instance. The best practice
- is to have the start_date rounded
- to your Dag's ``schedule_interval``. Daily jobs have their start_date
- some day at 00:00:00, hourly jobs have their start_date at 00:00
- of a specific hour. Note that Airflow simply looks at the latest
- ``logical_date`` and adds the ``schedule_interval`` to determine
- the next ``logical_date``. It is also very important
Review Comment:
Thanks, that makes sense. I restored the still-relevant guidance around
aligning `start_date` with the DAG schedule, while keeping the outdated
`schedule_interval`/logical-date scheduling description removed.
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
