[MDEV-21753] convert the upstream's '*-info-repository=TABLE' tables into info files Created: 2020-02-17  Updated: 2023-11-30

Status: Stalled
Project: MariaDB Server
Component/s: Replication
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Andrei Elkin Assignee: Andrei Elkin
Resolution: Unresolved Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-10047 Upgrade from MySQL to extract data in... Closed

 Description   

The upstream replication tables can be reused upon upgrade.
mysql_upgrade is required to be run after starting the new MariaDB server and it
will convert, through running SELECTs on the tables, the tables into replication configuration files
compatible with Mariadb slave format.

 Comments   
Comment by Andrei Elkin [ 2020-09-03 ]

As a intermediate result of running the desciption's SET:s we gain master.info relay-log.info still in the upstream format.
And then convert the intermediate result to Maria specific format.

Comment by Sujatha Sivakumar (Inactive) [ 2020-10-28 ]

Hello ralf.gebhardt@mariadb.com and ccalender

Please have a look at the following details, regarding what MDEV-21753 will address.

MDEV-10047 had 3 requirements.

R1) Issue a warning when 'mysql_upgrade' script ignores content of "mysql.slave_master_info" and mysql.slave_relay_log_info" tables.

R2) Migrate/Extract the data from 'mysql.slave_master_info' and 'mysql.slave_relay_log_info' to store them in master.info file.

R3) Support table based master info repository, so that Innodb table can be encrypted and password will not be in plain text form.

R1) - Fixed as part of MDEV-10047
R2) - Will be addressed as part of current MDEV-21753
R3) - For enhanced security, authentication plugin based solution needs to be used.

Thank you.

Generated at Thu Feb 08 09:09:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.