kzosabe commented on PR #34771:
URL: https://github.com/apache/airflow/pull/34771#issuecomment-1749839694
As I understood about this change (errors may be included, please give me
point it out):
- before this PR, `ti.start_date` was set at `RUNNING` phase as a result in
almost cases
- backfill is the one of exceptions, and there could be some other cases
- after this PR, `ti.start_date` will be set at `QUEUED` phase in almost
cases
- the time duration of `QUEUED` between `RUNNING` may be long in some cases
like all workers are busy
So there are some considerations of behaviour change about ti.start_date:
- some sql queries using ti.start_date for filtering task, etc.
- query results may change e.g. results ordering, or calucurated task
duration length, and so on
- some users that considering about start_date as started running time of
task will confused about this change
And I worried about should we treat the `ti.start_date` as `queued_date` or
`started_running_date` .
In the community, what do you think?
--
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]
