[MDEV-5476] Found Index PRIMARY whose column info does not match that of MySQL ENUM type Created: 2013-12-20  Updated: 2014-01-26  Due: 2014-01-21  Resolved: 2014-01-26

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: 5.5.34
Fix Version/s: 5.5.35

Type: Bug Priority: Major
Reporter: Luke Pascal Assignee: Sergei Golubchik
Resolution: Cannot Reproduce Votes: 0
Labels: None
Environment:

CentOS 6.2

Issue Links:
Duplicate
duplicates MDEV-4024 Found Index PRIMARY whose column info... Closed

 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



 Comments   
Comment by Elena Stepanova [ 2013-12-20 ]

Is there a typo in the bug number you were referring to?

Comment by Luke Pascal [ 2013-12-21 ]

Yes indeed. Is about MDEV-4024.

Seems that this bug exist in the rpm version for CentOS in MariaDB 5.5.34

Comment by Elena Stepanova [ 2013-12-22 ]

Thank you.

That's right, as you can see from MDEV-4024 (comments and "Affects Version/s" field), it existed in all of 5.3, 5.5, 10.0, but the fix was only applied to 10.0, as the "Fix Version/s" says.
Do you observe any damage to the data along with the warnings?

Comment by Luke Pascal [ 2013-12-24 ]

No damage. How can I bug fix 5.5 ? is 10.0 compatible with Mysql innodb raw partition ?

Comment by Luke Pascal [ 2013-12-24 ]

We tested 5.5 and is great. I just want to fix this . Can you help?

Comment by Elena Stepanova [ 2013-12-24 ]

Hi Sergei,

Do you remember why MDEV-4024 was only treated in 10.0 but not in 5.5? If I understand correctly, it wasn't that much of a fix as a cosmetic change, so probably it should be safe enough to do the same in 5.5?

Comment by Luke Pascal [ 2014-01-06 ]

Hi,

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

Comment by Sergei Golubchik [ 2014-01-06 ]

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.

Comment by Luke Pascal [ 2014-01-06 ]

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

Comment by Sergei Golubchik [ 2014-01-26 ]

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

Comment by Sergei Golubchik [ 2014-01-26 ]

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

Generated at Thu Feb 08 07:04:40 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.