mcilwain 7dc1940cdb Move ResaveAllEppResources mapreduce from tools service to backend ... It makes sense for all mapreduces to run in backend, especially onces that are scheduled regularly to run in cron like this one now. We don't have many instances configured for the tools service anymore on some of our environments, so backend is the friendliest place for a mapreduce to run. ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=168882122		2017-09-20 10:27:17 -04:00
..
BUILD	Add mapreduce cleanup action	2017-03-13 10:24:57 -04:00
DeleteContactsAndHostsActionTest.java	Add metrics for async batch operation processing	2017-06-05 18:17:09 -04:00
DeleteProberDataActionTest.java	Fix soft delete for possible double-map of domain	2017-09-12 14:57:34 -04:00
ExpandRecurringBillingEventsActionTest.java	Parent recurring billing events under separate HistoryEntries	2017-08-29 17:08:27 -04:00
MapreduceEntityCleanupActionTest.java	Refactor main loop of MapreduceEntityCleanupAction	2017-03-13 10:38:21 -04:00
RefreshDnsOnHostRenameActionTest.java	Add metrics for async batch operation processing	2017-06-05 18:17:09 -04:00
ResaveAllEppResourcesActionTest.java	Move ResaveAllEppResources mapreduce from tools service to backend	2017-09-20 10:27:17 -04:00
TestMapreduceEntityCleanupUtil.java	Add mapreduce cleanup action	2017-03-13 10:24:57 -04:00
VerifyEntityIntegrityActionTest.java	Fix some direct uses of ForeignKey(C/H/D)Index	2017-05-03 10:40:21 -04:00