This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new b31b8c08c4 Reflect drop/add support of DB Backends versions in
documentation (#35785)
b31b8c08c4 is described below
commit b31b8c08c490eb074e84f4870244a9396b485884
Author: Andrey Anshin <[email protected]>
AuthorDate: Wed Nov 22 01:43:16 2023 +0400
Reflect drop/add support of DB Backends versions in documentation (#35785)
---
.../administration-and-deployment/scheduler.rst | 14 ++++----------
docs/apache-airflow/howto/set-up-database.rst | 10 +++++++---
docs/apache-airflow/installation/prerequisites.rst | 11 +++--------
3 files changed, 14 insertions(+), 21 deletions(-)
diff --git a/docs/apache-airflow/administration-and-deployment/scheduler.rst
b/docs/apache-airflow/administration-and-deployment/scheduler.rst
index 06769d1595..a01020a686 100644
--- a/docs/apache-airflow/administration-and-deployment/scheduler.rst
+++ b/docs/apache-airflow/administration-and-deployment/scheduler.rst
@@ -118,7 +118,7 @@ This does, however, place some requirements on the Database.
Database Requirements
"""""""""""""""""""""
-The short version is that users of PostgreSQL 10+ or MySQL 8+ are all ready to
go -- you can start running as
+The short version is that users of PostgreSQL 12+ or MySQL 8.0+ are all ready
to go -- you can start running as
many copies of the scheduler as you like -- there is no further set up or
config options needed. If you are
using a different database please read on.
@@ -134,8 +134,8 @@ UPDATE NOWAIT`` but the exact query is slightly different).
The following databases are fully supported and provide an "optimal"
experience:
-- PostgreSQL 10+
-- MySQL 8+
+- PostgreSQL 12+
+- MySQL 8.0+
.. warning::
@@ -144,15 +144,9 @@ The following databases are fully supported and provide an
"optimal" experience:
Without these features, running multiple schedulers is not supported and
deadlock errors have been reported. MariaDB
10.6.0 and following may work appropriately with multiple schedulers, but
this has not been tested.
-.. warning::
-
- MySQL 5.x does not support ``SKIP LOCKED`` or ``NOWAIT``, and additionally
is more prone to deciding
- queries are deadlocked, so running with more than a single scheduler on
MySQL 5.x is not supported or
- recommended.
-
.. note::
- Microsoft SQLServer has not been tested with HA.
+ Microsoft SQL Server has not been tested with HA.
.. _fine-tuning-scheduler:
diff --git a/docs/apache-airflow/howto/set-up-database.rst
b/docs/apache-airflow/howto/set-up-database.rst
index 3c8f7a9bb1..b164552814 100644
--- a/docs/apache-airflow/howto/set-up-database.rst
+++ b/docs/apache-airflow/howto/set-up-database.rst
@@ -32,8 +32,8 @@ By default, Airflow uses **SQLite**, which is intended for
development purposes
Airflow supports the following database engine versions, so make sure which
version you have. Old versions may not support all SQL statements.
-* PostgreSQL: 11, 12, 13, 14, 15
-* MySQL: 5.7, 8
+* PostgreSQL: 12, 13, 14, 15, 16
+* MySQL: 8.0, `Innovation
<https://dev.mysql.com/blog-archive/introducing-mysql-innovation-and-long-term-support-lts-versions>`_
* MSSQL (Experimental, **Discontinued soon**): 2017, 2019
* SQLite: 3.15.0+
@@ -309,7 +309,11 @@ In addition, you also should pay particular attention to
MySQL's encoding. Altho
.. note::
- In strict mode, MySQL doesn't allow ``0000-00-00`` as a valid date. Then
you might get errors like ``"Invalid default value for 'end_date'"`` in some
cases (some Airflow tables use ``0000-00-00 00:00:00`` as timestamp field
default value). To avoid this error, you could disable ``NO_ZERO_DATE`` mode on
you MySQL server. Read
https://stackoverflow.com/questions/9192027/invalid-default-value-for-create-date-timestamp-field
for how to disable it. See `SQL Mode - NO_ZERO_DATE <https://dev [...]
+ In strict mode, MySQL doesn't allow ``0000-00-00`` as a valid date. Then
you might get errors like
+ ``"Invalid default value for 'end_date'"`` in some cases (some Airflow
tables use ``0000-00-00 00:00:00`` as timestamp field default value).
+ To avoid this error, you could disable ``NO_ZERO_DATE`` mode on you MySQL
server.
+ Read
https://stackoverflow.com/questions/9192027/invalid-default-value-for-create-date-timestamp-field
for how to disable it.
+ See `SQL Mode - NO_ZERO_DATE
<https://dev.mysql.com/doc/refman/8.0/en/sql-mode.html#sqlmode_no_zero_date>`__
for more information.
Setting up a MsSQL Database
---------------------------
diff --git a/docs/apache-airflow/installation/prerequisites.rst
b/docs/apache-airflow/installation/prerequisites.rst
index 3b8f5c84d9..f2fefbfbaa 100644
--- a/docs/apache-airflow/installation/prerequisites.rst
+++ b/docs/apache-airflow/installation/prerequisites.rst
@@ -24,10 +24,10 @@ Airflow™ is tested with:
* Databases:
- * PostgreSQL: 11, 12, 13, 14, 15
- * MySQL: 5.7, 8.0, 8.1
+ * PostgreSQL: 12, 13, 14, 15, 16
+ * MySQL: 8.0, `Innovation
<https://dev.mysql.com/blog-archive/introducing-mysql-innovation-and-long-term-support-lts-versions>`_
* SQLite: 3.15.0+
- * MSSQL(Experimental): 2017, 2019
+ * MSSQL (Experimental, **Discontinued soon**): 2017, 2019
* Kubernetes: 1.25, 1.26, 1.27, 1.28
@@ -43,11 +43,6 @@ wildly on the deployment options you have
attempts to use MariaDB as a backend and users cannot expect any community
support for it
because the number of users who tried to use MariaDB for Airflow is very
small.
-.. warning::
-
- MySQL 5.x versions are unable to or have limitations with
- running multiple schedulers -- please see:
:doc:`/administration-and-deployment/scheduler`.
-
.. warning::
SQLite is used in Airflow tests. Do not use it in production. We recommend
using the latest stable version of SQLite for local development.
