|
|
@@ -1,6 +0,0 @@
|
|
|
-# Ads migration notes
|
|
|
-
|
|
|
-- **Schema change** – `Ads` documents no longer store `adsModuleId`; the enum `adType` now sits directly on `Ads`.
|
|
|
-- **API compatibility** – mgnt endpoints still accept legacy `adsModuleId`, but the service resolves it to `adType` (logging a warning) and rejects when neither value is present. Once every caller switches to `adType`, you can remove the legacy branch.
|
|
|
-- **Data migration** – backfill every existing `Ads` record by copying `AdsModule.adType` into the new `adType` field, verify reads/writes no longer reference `adsModuleId`, and then retire the legacy key/payload mapping after caches flush.
|
|
|
-- **Cache migration** – `box:app:adpool:{adType}` and `app:ad:by-id:{adId}` now drive ad placement; legacy pools keyed by `adsModuleId` are only read once during fallback and should be pruned once the new adType-based caches are warm.
|