CODEWITHSUNDEEP
airflow
MrBronson
MrBronson

Reputation: 612

Airflow DeprecationWarning

I'm running a distributed Airflow 2.4.0 setup using the official Docker image. All the containers use the same .env file and same version of Airflow image. When I log into one of the Airflow containers I get this warning:

/home/airflow/.local/lib/python3.7/site-packages/airflow/configuration.py:545: DeprecationWarning: The sql_alchemy_conn option in [core] has been moved to the sql_alchemy_conn option in [database] - the old setting has been used, but please update your config.
  option = self._get_environment_variables(deprecated_key, deprecated_section, key, section)
/home/airflow/.local/lib/python3.7/site-packages/airflow/configuration.py:545: DeprecationWarning: The auth_backend option in [api] has been renamed to auth_backends - the old setting has been used, but please update your config.
  option = self._get_environment_variables(deprecated_key, deprecated_section, key, section)
/home/airflow/.local/lib/python3.7/site-packages/airflow/configuration.py:367: FutureWarning: The auth_backends setting in [api] has had airflow.api.auth.backend.session added in the running config, which is needed by the UI. Please update your config before Apache Airflow 3.0.
  FutureWarning,

I checked the airflow.cfg inside the container and it has the up to date variables. Why do I still get the warning messages?

Upvotes: 3

Views: 12490

Answers (1)

Elad Kalif
Elad Kalif

Reputation: 15931

You are seeing these warnings because of the section. airflow.cfg is configuration file with section. settings are expected to be in the proper section.

In your case your airflow.cfg has sql_alchemy_conn where you override the default value. Prior to 2.3.0 this setting in core section and in 2.3.0 it was moved to database section. (see PR)

What you need to do is simply open airflow.cfg and move the setting to the proper section. For example:

[core]

sql_alchemy_conn = sqlite:///{AIRFLOW_HOME}/airflow.db

to:

[database]

sql_alchemy_conn = sqlite:///{AIRFLOW_HOME}/airflow.db

The reason why it's like that is also explained in the docs. Airflow reference settings by environment variables of the format AIRFLOW__{SECTION}__{KEY} so in this case it will be: AIRFLOW__DATABASE__SQL_ALCHEMY_CONN so the section is important to find the variable.

Upvotes: 12

Related Questions