epriestley 8ad5d28686 Migrate old reviewer edges to new storage ... Summary: Ref T10967. We still have double writes, so all reviewers are being written to both old and new storage. This migrates all the data in the old storage to the new storage, so both storage tables should have a complete set of data and be getting identical updates as we move forward. After this, I can move readers over one at a time and eventually get rid of the old writes and old storage. This loads all of the edge data into memory in a big chunk. I reached out to one install to get some more information about their data size. Ours is quite manageable and I think even large installs will probably fit into memory, but we can do this in chunks if not. However, because the Edge table doesn't have an `id` column, we can't use either the `RawMigrationIterator` or the `MigrationIterator`, and would need to write a new `EdgeMigrationIterator`. This isn't tons of work but might not be necessary. Test Plan: Ran the migration locally, spot-checked the results in the database for sanity and correctness. Reviewers: chad Reviewed By: chad Maniphest Tasks: T10967 Differential Revision: https://secure.phabricator.com/D17515		2017-03-20 16:44:40 -07:00
..
autopatches	Migrate old reviewer edges to new storage	2017-03-20 16:44:40 -07:00
patches	Probably (?) fix two very old project slug migrations	2016-12-14 14:14:21 -08:00
quickstart.sql	Update quickstart.sql	2016-06-24 14:49:03 -07:00
stopwords.txt	Provide a setup warning about using the default MySQL stopword file	2014-08-13 15:34:09 -07:00