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

Found Index PRIMARY whose column info does not match that of MySQL ENUM type

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 5.5.34
    • 5.5.35
    • None
    • None
    • CentOS 6.2

    Description

      I found same issue as MDEV-4024 on 5.5.34 version when updating from Mysql to MariaDB using InnoDB raw partition.

      131220 11:35:01 [ERROR] Found index enabled whose column info does not match that of MySQL.
      		 
      131220 11:35:01 [ERROR] Build InnoDB index translation table for Table .......policy_test failed

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-4024 Found Index PRIMARY whose column info does not match that of MySQL

          • Major - Major loss of function.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            View 6 older comments
            sololuke2013 Luke Pascal added a comment -

            Hi,

            I would also need patch for 5.5.34 and src rpm. Is possible ? Where I can find this?

            sololuke2013 Luke Pascal added a comment - Hi, I would also need patch for 5.5.34 and src rpm. Is possible ? Where I can find this?
            serg Sergei Golubchik added a comment -

            The final patch is here: http://bazaar.launchpad.net/~maria-captains/maria/10.0/revision/3903
            but it won't apply cleanly to 5.5.

            Instead you can try to copy get_innobase_type_from_mysql_type() function from XtraDB to InnoDB.

            There is no source rpm, we build rpm packages from the source tree using cmake. See https://mariadb.com/kb/en/source-building-mariadb-on-centos/ for details.

            serg Sergei Golubchik added a comment - The final patch is here: http://bazaar.launchpad.net/~maria-captains/maria/10.0/revision/3903 but it won't apply cleanly to 5.5. Instead you can try to copy get_innobase_type_from_mysql_type() function from XtraDB to InnoDB. There is no source rpm, we build rpm packages from the source tree using cmake. See https://mariadb.com/kb/en/source-building-mariadb-on-centos/ for details.
            sololuke2013 Luke Pascal added a comment -

            Interesting is that when I force to use XtraDB I have same errors in log.

            sololuke2013 Luke Pascal added a comment - Interesting is that when I force to use XtraDB I have same errors in log.
            serg Sergei Golubchik added a comment -

            I cannot repeat that. I get the warning only with InnoDB, but not with XtraDB.

            serg Sergei Golubchik added a comment - I cannot repeat that. I get the warning only with InnoDB, but not with XtraDB.
            serg Sergei Golubchik added a comment -

            please, don't hesitate to reopen this bug report, if you have a complete repeatable test case

            serg Sergei Golubchik added a comment - please, don't hesitate to reopen this bug report, if you have a complete repeatable test case

            People

              serg Sergei Golubchik
              sololuke2013 Luke Pascal
              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.