Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-21753

convert the upstream"s "*-info-repository=TABLE" tables into info files

Details

    • New Feature
    • Status: Stalled (View Workflow)
    • Major
    • Resolution: Unresolved
    • None
    • Replication
    • None

    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.

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-10047 Upgrade from MySQL to extract data into master.info file WAS: table-based master info repository

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            Elkin Andrei Elkin added a comment -

            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.

            Elkin Andrei Elkin added a comment - 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.
            sujatha.sivakumar Sujatha Sivakumar (Inactive) added a comment -

            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.

            sujatha.sivakumar Sujatha Sivakumar (Inactive) added a comment - 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.

            People

              bnestere Brandon Nesterenko
              Elkin Andrei Elkin
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.