Not sure if the documentation is wrong or I am misunderstanding.
I assume the automatic upgrade is done on patch not minor ?
or it is correct minor version i.e. 10.2.x -> 10.3.x will be handled automatically ?
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@ahelal We are checking this and will get back to you regarding this.
@ahelal I am not sure I fully understand the question but here is information on what I understood. Currently patching will update only the minor versions inside a major version. Major versions being 10.2 and 10.3.
So the patching will only change 10.2.x to 10.2.y or 10.3.x to 10.3.y. The update from 10.2.x to 10.3.y is not supported.
Here is the document that explains the limitations for Azure DB for MariaDB. It explains the limitation of server version upgrade where it says:
"Automated migration between major database engine versions is currently not supported."
https://docs.microsoft.com/en-us/azure/mariadb/concepts-limits#functional-limitations
Hope this helps. If I have misunderstood the question, please elaborate and we will try to help regarding the same.
@ahelal Please let us know if you have any other issue in this regard or we will go ahead and close the thread for now.
@NavtejSaini-MSFT that is my question. if that is semantic version MAJOR.MINOR.PATCH
the wording would be "we only support upgrades on PATCH" not minor versions.
like the Azure MYSQL doc
Or am I confusing something fundamental ?
Cheers.
@ahelal - you are correct. The wording in the MariaDB doc is incorrect and should match the wording in the MySQL doc. I will submit a doc fix shortly.
@ajlam Thanks for the information and changes to the doc.
@ahelal It will take sometime for changes to reflect. Once the doc is updated we will close this thread.
PR was merged and changes should be live in about 4-5 hours.
thank you both @ajlam @NavtejSaini-MSFT for your quick response 👍
Most helpful comment
@ahelal - you are correct. The wording in the MariaDB doc is incorrect and should match the wording in the MySQL doc. I will submit a doc fix shortly.