pt-online-schema-change: typo for finding usable indexes

[Paul Golownia]

show create table_name;

CREATE TABLE ` table_name` (
  `site` varchar(20) NOT NULL DEFAULT '',
  `update_name` varchar(32) NOT NULL DEFAULT '',
  `user` varchar(64) NOT NULL DEFAULT '',
  `time` datetime NOT NULL DEFAULT '0000-00-00 00:00:00',
  `type` enum('aaa','bbb','ccc','ddd') NOT NULL DEFAULT 'update',
  `value` varchar(64) NOT NULL DEFAULT '',
  UNIQUE KEY `site` (`site`,`update_name`,`user`,`value`),
  KEY `user` (`user`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1

Error:

The original table `db`.`table_name` does not have a PRIMARY KEY or a unique index which is required for the DELETE trigger.

This appears to be a typo when looking for unique or primary keys in the table def. should be keys NOT indexes

 Fixed with the following patch:

6184c6184
< my $indexes = $orig_tbl->{tbl_struct}->{keys}; # brevity
---
> my $indexes = $orig_tbl->{tbl_struct}->{indexes}; # brevity

[Daniel Nichter (daniel-nichter)]

Good catch, thank you.

[Daniel Nichter (daniel-nichter)]

Also reported as bug 1002849.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PT-533