CODEWITHSUNDEEP
templatesparametersjinja2operator-keywordairflow
robinhur
robinhur

Reputation: 113

How can I get execution_date in dag?? the outside of operator?

How can I get an execution_date parameter in outside of dag?

execution_min = "{{execution_date.strftime('%M') }}"

if execution_min == '00':
    logging.info('**** ' + "YES, It's 00")
    final_task = DummyOperator(
        task_id='task_y00',
        ...
        dag=dag
    )
else:
    logging.info('**** ' + "NOPE!!!")
    final_task = DummyOperator(
        task_id='task_n00',
        ...
        dag=dag
    )

I want to set a task stream with dynamically with execution_date (especially minute)

But Jinja template won't work with template_fields = ['execution_date']

Are there any solutions to get the execution parameter from outside of operator (= in the DAG itself) ???

Upvotes: 9

Views: 16686

Answers (2)

Chengzhi
Chengzhi

Reputation: 2591

Try to just use execution_min = "{{ execution_date }}" then strftime after, make sure you have space before and after double braces.

UPDATE: If you are using it outside of the Operator, it won't work, you can pass a kwargs in then use it. Airflow: pass {{ ds }} as param to PostgresOperator

Upvotes: 1

jhnclvr
jhnclvr

Reputation: 9487

Execution date is specific to a DagRun. DagRun information is not available in a DAG definition file (it is available in an Operator's template fields because these get parsed at run-time via Jinja). DAG definition files are parsed frequently by the scheduler, webserver and workers even when the dag isn't running. This is why outside of an actual DagRun there is no access to things like execution date.

Furthermore there is no way to add/subtract tasks to a DAG run at runtime. You can have dynamic dags whose structure is decided before they run (ie. parse a file into a DAG structure), but you can't add tasks or decide what a DAG looks like while it's running.

Upvotes: 7

Related Questions