potiuk commented on code in PR #33038: URL: https://github.com/apache/airflow/pull/33038#discussion_r1284334237
########## RELEASE_NOTES.rst: ########## @@ -21,6 +21,296 @@ .. towncrier release notes start +Airflow 2.7.0 (2023-08-10) +-------------------------- + +Significant Changes +^^^^^^^^^^^^^^^^^^^ + +Remove Python 3.7 support (#30963) +"""""""""""""""""""""""""""""""""" +As of now, Python 3.7 is no longer supported by the Python community. +Therefore, to use Airflow 2.7.0, you must ensure your Python version is +either 3.8, 3.9, 3.10, or 3.11. + +Old Graph View is removed (#32958) +"""""""""""""""""""""""""""""""""" +The old Graph View is removed. The new Graph View is the default view now. + +In case of SMTP SSL connection, the default context now uses "default" context (#33070) +""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" +The "default" context is Python's ``default_ssl_contest`` instead of previously used "none". The +``default_ssl_context`` provides a balance between security and compatibility but in some cases, +when certificates are old, self-signed or misconfigured, it might not work. This can be configured +by setting "ssl_context" in "email" configuration of Airflow. Setting it to "none" brings back +the "none" setting that was used in Airflow 2.6 and before, but it is not recommended due to security +reasons ad this setting disables validation of certificates and allows MITM attacks. + +Disable default allowing the testing of connections in UI, API and CLI(#32052) +"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" +For security reasons, the test connection functionality is disabled by default across Airflow UI, +API and CLI. The availability of the functionality can be controlled by the +``test_connection`` flag in the ``core`` section of the Airflow +configuration (``airflow.cfg``). It can also be controlled by the +environment variable ``AIRFLOW__CORE__TEST_CONNECTION``. +The following values are accepted for this config param: +1. ``Disabled``: Disables the test connection functionality and +disables the Test Connection button in the UI. +This is also the default value set in the Airflow configuration. +2. ``Enabled``: Enables the test connection functionality and +activates the Test Connection button in the UI. +3. ``Hidden``: Disables the test connection functionality and +hides the Test Connection button in UI. +For more information on capabilities of users, see the documentation: +https://airflow.apache.org/docs/apache-airflow/stable/security/security_model.html#capabilities-of-authenticated-ui-users +It is strongly advised to **not** enable the feature until you make sure that only +highly trusted UI/API users have "edit connection" permissions. +The ``xcomEntries`` API disables support for the ``deserialize`` flag by default (#32176) +""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" +For security reasons, the ``/dags/*/dagRuns/*/taskInstances/*/xcomEntries/*`` +API endpoint now disables the ``deserialize`` option to deserialize arbitrary +XCom values in the webserver. For backward compatibility, server admins may set +the ``[api] enable_xcom_deserialize_support`` config to *True* to enable the +flag and restore backward compatibility. + +However, it is strongly advised to **not** enable the feature, and perform +deserialization at the client side instead. + +Default name of the Celery application changed from ``airflow.executors.celery_executor`` to ``airflow.providers.celery.executors.celery_executor`` (#32526) +"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" +You should change both your configuration and Health check command to use the new name: + * in configuration (``celery_app_name`` configuration in ``celery`` section) use ``airflow.providers.celery.executors.celery_executor`` + * in your Health check command use ``airflow.providers.celery.executors.celery_executor.app`` + + +The default value for ``scheduler.max_tis_per_query`` is changed from 512 to 16 (#32572) +"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""" +This change is expected to make the Scheduler more responsive. + +``scheduler.max_tis_per_query`` needs to be lower than ``core.parallelism``. +If both were left to their default value previously, the effective default value of ``scheduler.max_tis_per_query`` was 32 +(because it was capped at ``core.parallelism``). + +To keep the behavior as close as possible to the old config, one can set ``scheduler.max_tis_per_query = 0``, +in which case it'll always use the value of ``core.parallelism``. + +The Kubernetes, Celery, CeleryKubernetes, LocalKubernetes, and Dask executors are moved to corresponding providers (#32767) Review Comment: Same here. I think the header should be: ``Some executors have been moved to providers`` or smth like that. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
