Warning Issue for MariaDB Versions Supported by DM

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: DM支持的MariaDB版本警告问题

| username: Jaimyjie

[TiDB Usage Environment] Production Environment / Testing / Poc
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots / Logs / Monitoring]

Will there still be a warning prompt if the source data MariaDB version for DM synchronization meets the requirements (10.4.8, greater than the required 10.1.2)?

{
“id”: 0,
“name”: “mysql_version”,
“desc”: “check whether mysql version is satisfied”,
“state”: “warn”,
“errors”: [
{
“severity”: “warn”,
“short_error”: “Migrating from MariaDB is experimentally supported. If you must use DM to migrate data from MariaDB, we suggest making your MariaDB \u003e= 10.1.2”
}
],

2
| username: magic | Original post link

The warning shouldn’t affect usage, right? Could there be any pitfalls?

3
| username: 我是咖啡哥 | Original post link

MariaDB is at most experimentally supported. Therefore, it cannot be guaranteed to be problem-free.

4
| username: xingzhenxiang | Original post link

The language logic is rigorous :innocent:

5
| username: okenJiang | Original post link

It is just a suggested version. DM has not yet completed comprehensive testing for MariaDB, so it is still an experimental feature.