Add information about drop support MsSQL as DB Backend in the future #34375
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Taragolis
requested review from
potiuk,
ephraimbuddy,
kaxil,
hussein-awala and
eladkal
Taragolis
force-pushed
the
do-not-recommend-mssql
branch
from
c679a22 to
22a86c1
Compare
If somoene implements the removal and migration solution to Postgres- yes. The condition of dropping MSSQL was to get a tool that will help MSSQL users to migrate to Postgres, so we have to implement it. |
|
Let's explain my motivation for add it now, even if we drop in 2.8.0. User who make chouse MsSQL at 2.7.2 actually make non-obvious selection for Postgres 🤣 |
Yes. We shoudl definitely add the information now. And also mark it clearly as deprecated for 2.7.2 |
potiuk
approved these changes
Sep 14, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.