pt-upgrade has Maatkit legacy values

Bug #928225 reported by Baron Schwartz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Toolkit moved to https://jira.percona.com/projects/PT
Invalid
Undecided
Unassigned
2.1
Won't Fix
Undecided
Unassigned
2.2
Invalid
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

Tags: pt-upgrade
Changed in percona-toolkit:
importance: Medium → Undecided
Revision history for this message
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.

Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

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

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.