Page MenuHomePhabricator

Allow `bin/storage adjust` to adjust table engines
ClosedPublic

Authored by epriestley on Nov 24 2016, 5:08 PM.
Tags
None
Referenced Files
F14004460: D16941.diff
Sat, Oct 26, 8:56 PM
F13987790: D16941.id40774.diff
Mon, Oct 21, 11:19 AM
F13970765: D16941.id40785.diff
Thu, Oct 17, 9:45 AM
Unknown Object (File)
Oct 9 2024, 6:22 AM
Unknown Object (File)
Oct 8 2024, 2:38 AM
Unknown Object (File)
Oct 7 2024, 10:48 PM
Unknown Object (File)
Oct 2 2024, 10:31 PM
Unknown Object (File)
Oct 2 2024, 8:04 AM
Subscribers
None

Details

Summary

Ref T11741. On recent-enough versions of MySQL, we would prefer to use InnoDB for fulltext indexes instead of MyISAM.

Allow bin/storage adjust to read actual and expected table engines, and apply adjustments as necessary.

We have one existing bad table that uses the wrong engine, metamta_applicationemail. This change corrects that table.

Test Plan
  • Ran bin/storage upgrade.
  • Saw the adjustment phase apply this change properly:
>>>[463] <query> ALTER TABLE `local_metamta`.`metamta_applicationemail` COLLATE = 'utf8mb4_bin', ENGINE = 'InnoDB'

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Allow `bin/storage adjust` to adjust table engines.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Nov 24 2016, 5:18 PM
This revision was automatically updated to reflect the committed changes.