potiuk opened a new pull request #21205:
URL: https://github.com/apache/airflow/pull/21205


   After releasing 3.4.4 we can finally migrate to SQLAlchemy 1.4,
   however SQLAlchemy 1.4 removed the use of postgres:// as valid
   specification for Postgres DB SQL (leaving only postgresql://)
   
   Due to that we need to change:
   
   * postgres provider to return postgresql:// with get_db_uri()
   * fix a number of tests that expected postgres://
   
   We cannot do much if someone uses postgres:// specification.
   Technically it might be seen as breaking change, but this is not
   an airflow breaking change and users could still use SQLAlchemy
   1.3 to keep the old prefix, so we can introduce this change
   in Airflow without raising the major version.
   
   <!--
   Thank you for contributing! Please make sure that your code changes
   are covered with tests. And in case of new features or big changes
   remember to adjust the documentation.
   
   Feel free to ping committers for the review!
   
   In case of existing issue, reference it using one of the following:
   
   closes: #ISSUE
   related: #ISSUE
   
   How to write a good git commit message:
   http://chris.beams.io/posts/git-commit/
   -->
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
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]


Reply via email to