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


   There was a change in #16521 that introduced schema field in
   DBApiHook, but unfortunately using it in provider Hooks deriving
   from DBApiHook is backwards incompatible for Airflow 2.1 and below.
   
   This caused Postgres 2.1.0 release backwards incompatibility and
   failures for Airflow 2.1.0.
   
   Since the change is small and most of DBApi-derived hooks already
   set the schema field on their own, the best approach is to
   make the schema field private for the DBApiHook and make a change
   in Postgres Hook to store the schema in the same way as all other
   operators.
   
   Fixes: #17422
   
   <!--
   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