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

Don't require .cfg files to import InnoDB tablespaces

Details

    Description

      FLUSH TABLES ... FOR EXPORT creates a .cfg file that is supposed to be copied and imported along with the .ibd file. These .cfg files are not always needed.

      However, the .cfg files are absolutely needed in some cases, such as:

      • If you want your AUTO_INCREMENT value to be populated properly on import, then you need to copy the .cfg file (MDEV-18288).
      • If you want to avoid the potential risk of server crashes, then you need to copy the .cfg file to avoid some bugs (MDEV-14342 and MDEV-20931).
      • What other cases are there?

      And the .cfg files can also be very helpful for troubleshooting in some cases, such as:

      • If the row format is different between the source server and the destination server, then you need to copy the .cfg file if you want to see a more clear error message (MDEV-15049 and MDEV-16851).

      Would it be possible to make the .cfg files completely unnecessary?

      Attachments

        Issue Links

          duplicates

          New Feature - A new feature of the product, which has yet to be developed. MDEV-11658 Simpler, faster IMPORT of InnoDB tables

          • Critical - Crashes, loss of data, severe memory leak.
          • Open
          includes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-15225 Can't import .ibd file with temporal type format differing from mysql56_temporal_format

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-14342 Importing partial backup from XtraBackup can sometimes crash server

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-15049 Importing InnoDB table from 10.1 to 10.2 causes Schema mismatch (Expected FSP_SPACE_FLAGS=0x21, .ibd file contains 0x0

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-16851 On schema mismatch in IMPORT TABLESPACE, display ROW_FORMAT in clear text

          • Major - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-18288 Transportable Tablespaces leave AUTO_INCREMENT in mismatched state, causing INSERT errors in newly imported tables when .cfg is not used.

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20930 Document that SHOW CREATE TABLE on InnoDB tables only shows ROW_FORMAT when explicitly set

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. MDEV-20931 ALTER...IMPORT can crash the server

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            marko Marko Mäkelä added a comment - - edited

            I think that this request is duplicating much of what has been already described in MDEV-11658.

            In MDEV-11658, I wrote that a change of the .ibd file format is necessary to allow secondary indexes to be safely imported without a .cfg file.

            marko Marko Mäkelä added a comment - - edited I think that this request is duplicating much of what has been already described in MDEV-11658 . In MDEV-11658 , I wrote that a change of the .ibd file format is necessary to allow secondary indexes to be safely imported without a .cfg file.
            GeoffMontee Geoff Montee (Inactive) added a comment -

            marko,

            MDEV-15225 and this issue (MDEV-20974) seem a bit different to me. However, maybe MDEV-15225 could technically be considered a subset of this feature request.

            The description of MDEV-15225 is specifically about being able to import a tablespace created with a different mysql56_temporal_format value.

            The description of this issue (MDEV-20974) is about being able to import tablespaces without .cfg files in all cases. This seems to involve more than the secondary index changes that you mentioned in MDEV-15225. The description of this issue mentions two more kinds of changes that may be required that I know of:

            • If you want your AUTO_INCREMENT value to be populated properly on import, then you need to copy the .cfg file (MDEV-18288).
              ...
            • If the row format is different between the source server and the destination server, then you need to copy the .cfg file if you want to see a more clear error message (MDEV-15049 and MDEV-16851).

            As far as I can tell, these two cases would not be fixed by the secondary index changes mention in MDEV-15225, so it doesn't look like MDEV-15225 covers all of the changes that this issue is requesting. If we want to merge this issue with MDEV-15225, then we might need to enhance the description of MDEV-15225.

            GeoffMontee Geoff Montee (Inactive) added a comment - marko , MDEV-15225 and this issue ( MDEV-20974 ) seem a bit different to me. However, maybe MDEV-15225 could technically be considered a subset of this feature request. The description of MDEV-15225 is specifically about being able to import a tablespace created with a different mysql56_temporal_format value. The description of this issue ( MDEV-20974 ) is about being able to import tablespaces without .cfg files in all cases. This seems to involve more than the secondary index changes that you mentioned in MDEV-15225 . The description of this issue mentions two more kinds of changes that may be required that I know of: If you want your AUTO_INCREMENT value to be populated properly on import, then you need to copy the .cfg file ( MDEV-18288 ). ... If the row format is different between the source server and the destination server, then you need to copy the .cfg file if you want to see a more clear error message ( MDEV-15049 and MDEV-16851 ). As far as I can tell, these two cases would not be fixed by the secondary index changes mention in MDEV-15225 , so it doesn't look like MDEV-15225 covers all of the changes that this issue is requesting. If we want to merge this issue with MDEV-15225 , then we might need to enhance the description of MDEV-15225 .
            GeoffMontee Geoff Montee (Inactive) added a comment -

            Closing this as a duplicate of MDEV-11658.

            GeoffMontee Geoff Montee (Inactive) added a comment - Closing this as a duplicate of MDEV-11658 .

            People

              ralf.gebhardt Ralf Gebhardt
              GeoffMontee Geoff Montee (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

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