pt-upgrade has Maatkit legacy values

Reported by Baron Schwartz on 2012-02-07
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit
Status tracked in 2.2
2.1
Undecided
Unassigned
2.2
Undecided
Unassigned

Bug Description

pt-upgrade hasn't forgotten about Maatkit yet. This doesn't cause any problems, but it would be nicer if all of the tables it creates, etc were pt-prefixed. To verify,

$ grep mk pt-upgrade
   my $left_tbl = "`$db`.`mk_upgrade_left`";
   my $right_tbl = "`$db`.`mk_upgrade_right`";
      left_tbl => 'mk_upgrade_left',
      right_tbl => 'mk_upgrade_right',
         tbl => 'mk_upgrade_left',
         tbl => 'mk_upgrade_right',
L<"--temp-database"> called C<mk_upgrade_clear_warnings>.
Do C<CREATE TEMPORARY TABLE `mk_upgrade` AS query> then
C<CHECKSUM TABLE `mk_upgrade`>. This method is fast and simple but in
type: string; default: mk_upgrade

Changed in percona-toolkit:
importance: Medium → Undecided
Daniel Nichter (daniel-nichter) wrote :

pt-upgrade was completely re-written for 2.2. This issue is no longer valid and it won't be fixed in 2.1.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers