Bug #78306 | Unique Key is partially dropped from mysqld even when a 'drop index' fails | ||
---|---|---|---|
Submitted: | 2 Sep 2015 14:26 | Modified: | 5 Jan 2016 15:01 |
Reporter: | Lakshmi Narayanan Sreethar | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Cluster: Disk Data | Severity: | S3 (Non-critical) |
Version: | 7.4 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[2 Sep 2015 14:26]
Lakshmi Narayanan Sreethar
[5 Jan 2016 15:01]
Jon Stephens
Documented fix in the NDB 7.4.9 changelog, as follows: A unique index on a column of an NDB table has an internal ordered index, used for scanning. While dropping an index, this ordered index was dropped first, followed by the drop of the unique index itself. This meant that, when the drop was rejected due to a constraint violation, the statement was rejected but the associated ordered index remained deleted, so that any subsequent operation using a scan on this table failed. We fix this problem by causing the unique index to be removed first, before removing the ordered index; removal of the related ordered index is no longer performed when removal of a unique index fails. Closed.