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

PARTITION - Problem with CONNECT/ARIA frm file - mariadb 10.0.x

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.0.2, 10.0.3
    • 10.0.4, 5.5.32
    • None
    • None
    • LINUX 64

    Description

      Hi guys, i got a problem with a PARTITION TABLE being read as "CONNECT" engine ?!
      here is the files
      http://www.spadim.com.br/est_mov_v2.tgz

      and here the show status:

      Name Engine Version Row_format Rows Avg_row_length Data_length Max_data_length Index_length Data_free Auto_increment Create_time Update_time Check_time Collation Checksum Create_options Comment
      est_mov_v2 CONNECT 10 Dynamic 0 0 0 0 0 0 \N \N \N \N latin1_swedish_ci \N partitioned

      i don't know how to reproduce, i was using it normally and it was changed, i don't know why

      Attachments

        Issue Links

          Activity

            hi elena i editted the comment, please review if i made something wrong or changed the information about you reply

            rspadim roberto spadim added a comment - hi elena i editted the comment, please review if i made something wrong or changed the information about you reply

            No, the answer remains the same – it is likely the same problem as in MDEV-4466.
            For your questions about how SHOW CREATE TABLE works etc., you can always read the code and find out, it's a benefit of open-source

            elenst Elena Stepanova added a comment - No, the answer remains the same – it is likely the same problem as in MDEV-4466 . For your questions about how SHOW CREATE TABLE works etc., you can always read the code and find out, it's a benefit of open-source

            i think that's the important part that we could check / maybe develop a tool for it:


            1)in frm file, it's saved as CONNECT engine?
            a)what is write in file (via notepad or nano or vim)? (there's a tool to check this without mysqld running? something like:
            mysqld_read_frm_information frm_file_name.frm

            FILE: frm_file_name.frm
            FILE FORMAT WITHOUT MYSQLD: (it's a function external of mysqld code, like a external tool)
            ENGINE: ARIA PARTITIONED
            CREATE TIME: xxxxx
            others .frm informations: xxxxx

            FILE FORMAT READ BY MYSQLD: (it's the same function of mysqld we are running - 10.0.2 in this case)
            ENGINE: CONNECT PARTITIONED

            just to help us in debug
            maybe we could put it in mariadb.org/file-format.php, where we can send a .frm file (max of 100kb) and get information about it without a mysqld running)

            i will create a MDEV for it

            2) what SHOW CREATE TABLE use to rewrite the CREATE TABLE SQL?
            it's using the frm file information?
            why SHOW CREATE TABLE report right ARIA engine, and SHOW TABLE STATUS report CONNECT engine?
            they use two different functions?

            3)frm file with wrong format could crash server???
            that's the main problem, think about a file being copied to mariadb filesystem and it crash the server!
            server should mark it as UNKNOWN file format and leave it in filesystem and don't report it as a table
            the same happen when a frm file crash (maybe no energy or other problem) and mysqld crash too

            rspadim roberto spadim added a comment - i think that's the important part that we could check / maybe develop a tool for it: 1)in frm file, it's saved as CONNECT engine? a)what is write in file (via notepad or nano or vim)? (there's a tool to check this without mysqld running? something like: mysqld_read_frm_information frm_file_name.frm FILE: frm_file_name.frm FILE FORMAT WITHOUT MYSQLD: (it's a function external of mysqld code, like a external tool) ENGINE: ARIA PARTITIONED CREATE TIME: xxxxx others .frm informations: xxxxx FILE FORMAT READ BY MYSQLD: (it's the same function of mysqld we are running - 10.0.2 in this case) ENGINE: CONNECT PARTITIONED just to help us in debug maybe we could put it in mariadb.org/file-format.php, where we can send a .frm file (max of 100kb) and get information about it without a mysqld running) i will create a MDEV for it 2) what SHOW CREATE TABLE use to rewrite the CREATE TABLE SQL? it's using the frm file information? why SHOW CREATE TABLE report right ARIA engine, and SHOW TABLE STATUS report CONNECT engine? they use two different functions? 3)frm file with wrong format could crash server??? that's the main problem, think about a file being copied to mariadb filesystem and it crash the server! server should mark it as UNKNOWN file format and leave it in filesystem and don't report it as a table the same happen when a frm file crash (maybe no energy or other problem) and mysqld crash too

            MDEV of (1) is MDEV-4637

            rspadim roberto spadim added a comment - MDEV of (1) is MDEV-4637

            Fixed along with MDEV-4466

            elenst Elena Stepanova added a comment - Fixed along with MDEV-4466

            People

              Unassigned Unassigned
              rspadim roberto spadim
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.