[
https://issues.apache.org/jira/browse/AIRFLOW-4495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
t oo updated AIRFLOW-4495:
--------------------------
Description:
1.
useful to handle future date for externally triggered batch process where
ingesting 'forecast' data where filename date is in the future
2.
this error is just in the scheduler log and not propagated up, so the dag
stays in 'running' state forever (or for 1 year waiting for the time to pass :)
)
ERROR - Execution date is in future: 2020-01-01 00:00:00+00:00
fix below works if u only have externally triggered DAGs:
commenting below ti_deps\deps\runnable_exec_date_dep.py
#if ti.execution_date > cur_date:
# yield self._failing_status(
# reason="Execution date \{0} is in the future (the current "
# "date is \{1}).".format(ti.execution_date.isoformat(),
# cur_date.isoformat()))
commenting below jobs.py
# don't consider runs that are executed in the future
#if run.execution_date > timezone.utcnow():
# self.log.error(
# "Execution date is in future: %s",
# run.execution_date
# )
# continue
was:
1.
useful to handle future date for externally triggered batch process where
ingesting 'forecast' data where filename date is in the future
2.
this error is just in the scheduler log and not propagated up, so the dag stays
in 'running' state forever (or for 1 year waiting for the time to pass :) )
ERROR - Execution date is in future: 2020-01-01 00:00:00+00:00
> allow externally triggered dags to run for future 'Execution date'
> ------------------------------------------------------------------
>
> Key: AIRFLOW-4495
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4495
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: t oo
> Priority: Minor
>
> 1.
> useful to handle future date for externally triggered batch process where
> ingesting 'forecast' data where filename date is in the future
> 2.
> this error is just in the scheduler log and not propagated up, so the dag
> stays in 'running' state forever (or for 1 year waiting for the time to pass
> :) )
> ERROR - Execution date is in future: 2020-01-01 00:00:00+00:00
>
>
> fix below works if u only have externally triggered DAGs:
>
> commenting below ti_deps\deps\runnable_exec_date_dep.py
> #if ti.execution_date > cur_date:
> # yield self._failing_status(
> # reason="Execution date \{0} is in the future (the current "
> # "date is \{1}).".format(ti.execution_date.isoformat(),
> # cur_date.isoformat()))
>
> commenting below jobs.py
> # don't consider runs that are executed in the future
> #if run.execution_date > timezone.utcnow():
> # self.log.error(
> # "Execution date is in future: %s",
> # run.execution_date
> # )
> # continue
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
