What to do when Airflow BashOperator fails with TemplateNotFound error
Airflow has an annoying error that causes a failure when we try to use the BashOperator like this:
1 2 3 4 operator = BashOperator( task_id='operator_id', bash_command='some_bash_script.sh', dag=dag)
What is wrong? For some reason, it tries to apply the template variables to the “bash_command” parameter even if we don’t use them. Consequently, the template loader fails with the TemplateNotFound error because it cannot find any template variables in the given string.
Of course, in this case, it is the correct behavior because we don’t use any template variables. Unfortunately, it is not the behavior we want.
To make Airflow ignore the missing template and just use the given string as the file name (as it should do anyway), we have to trick the template parsing code by adding a single space at the end of the parameter:
1 2 3 4 operator = BashOperator( task_id='operator_id', bash_command='some_bash_script.sh ', dag=dag)
You may also like
- Why does the ExternalTaskSensor get stuck?
- Get the date of the previous successful DAG run in Airflow.
- How to postpone Airflow DAG until files get uploaded into an S3 bucket
- How to use AWSAthenaOperator in Airflow to verify that a DAG finished successfully
- How to use Virtualenv to prepare a separate environment for Python function running in Airflow