From c27a1e26c42d8e3a4cd320460ca00c7a90cd5a91 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=BB=84=E8=87=AA=E8=BE=BE?= <980324341@qq.com> Date: Sun, 27 Sep 2026 11:25:23 +0800 Subject: [PATCH] =?UTF-8?q?chore(=E8=BF=81=E7=A7=BB):=20=E6=96=B0=E5=A2=9E?= =?UTF-8?q?=20V136=20=E7=89=88=E6=9C=AC=E8=A1=A8=20is=5Flatest=E3=80=81V13?= =?UTF-8?q?7=20=E9=9A=90=E8=97=8F=2020=20=E4=B8=AA=E5=86=97=E4=BD=99?= =?UTF-8?q?=E7=B4=A2=E5=BC=95=EF=BC=9B=E7=99=BB=E8=AE=B0=20V132/V133=20?= =?UTF-8?q?=E9=80=80=E5=BD=B9=E7=A9=BA=E5=8F=B7?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 两个迁移原本按 V132/V133 取号,但生产 flyway_schema_history 已执行到 V135(V134/V135 于 2026-09-25 落库),应用没开 out-of-order,低号新迁移会让 validate-on-migrate 直接报 "Detected resolved migration not applied to database" 并启动失败,因此顺排到 V136/V137。 空号无法回收,MigrationInventoryTest 的「1..N 连续」断言改为显式登记 RETIRED_HOLES, 并要求迁移清单文档记录空号来历——否则后来人会试图回填这两个号。 V136:web_config 只追加、从不记录哪条是最新版,读取侧靠 ORDER BY created_at DESC 现场算; 一旦有人补插 created_at 较早的行,/api/version/latest 会把全体客户端指回旧包且不报错。 回填语句按同一排序取一行、不写死 id,迁移前后接口返回值逐字节一致。 V137:20 个「列是另一索引严格左前缀」的二级索引置 INVISIBLE 而非 DROP——前缀规则只保证 可用性不保证代价相同,且 aiimage 账号读不了 performance_schema(1142),没法先量出哪些查询 真在做覆盖扫描,所以先隐藏观察,一条语句即可还原。 --- backend-java/docs/migration-inventory.md | 20 +- .../db/V136__web_config_add_is_latest.sql | 60 ++++++ ...V137__hide_redundant_indexes_invisible.sql | 194 ++++++++++++++++++ .../config/MigrationInventoryTest.java | 30 ++- 4 files changed, 292 insertions(+), 12 deletions(-) create mode 100644 backend-java/src/main/resources/db/V136__web_config_add_is_latest.sql create mode 100644 backend-java/src/main/resources/db/V137__hide_redundant_indexes_invisible.sql diff --git a/backend-java/docs/migration-inventory.md b/backend-java/docs/migration-inventory.md index 45d62127d..2df87f3a8 100644 --- a/backend-java/docs/migration-inventory.md +++ b/backend-java/docs/migration-inventory.md @@ -1,22 +1,28 @@ # Flyway 迁移盘点(task-193) > 生成方式:`src/test/java/com/nanri/aiimage/config/MigrationInventoryTest.java`(只读审计,可重复)。 -> 快照日期:2026-09-05。 +> 快照日期:2026-09-27。 ## 概览 -- 版本化迁移文件数:**110**(`src/main/resources/db/V*.sql`) -- 整数版本范围:**V1..V109 连续** +- 版本化迁移文件数:**136**(`src/main/resources/db/V*.sql`) +- 整数版本范围:**V1..V137**,其中 V132/V133 为已退役空号(见下),其余连续 - 历史遗留小版本:**V25_1__shop_manage_group_bind_user.sql**(Flyway 语义 25.1,紧跟在 V25 之后、V26 之前执行,属历史命名,保留) -- 最新版本:**V109__admin_menu_frontend_routes.sql** +- 最新版本:**V137__hide_redundant_indexes_invisible.sql** - 重复版本:无 - 迁移命名:全部符合 `V<整数>(_<子版本>)?__<描述>.sql`,无空格 ## 生产已执行核对 -生产 Flyway 已执行到 ≥ V108;本次新增迁移使用 V109(迁移只追加,不回滚历史);新增迁移一律在 V108 之上取 `V109__*`,头注释引用 `docs/flyway-migration-template.md`(task-192)。 +生产 `flyway_schema_history` 末段:V125..V131 之后直接是 **V134__publish_item_free_text_columns**、**V135__dedupe_total_data_wide_columns**(两条 `installed_on` 均为 2026-09-25 20:46:16),库内没有 132/133 记录。 + +## V132/V133 空号的来历 + +本地曾存在 `V132__web_config_add_is_latest.sql`、`V133__hide_redundant_indexes_invisible.sql`,与另一分支已在生产落库的 V134/V135 冲突。因 Flyway 未开启 `out-of-order`,把任何迁移编到 132/133 会在启动期报 "resolved migration not applied";因此这两条改为 **V136/V137**,132/133 永久退役,不可回填。 + +后续新增迁移从 **V138** 起取号。 ## 约束 -- 审计测试断言:整数版本从 1 到当前最大值连续、无重复文件名、命名正则合规、历史文件校验和可复算稳定。 -- 修改任何已部署历史迁移会破坏 Flyway checksum,属违规;由本盘点测试的 `no_legacy_modified` 类约束 + code review 把关(git 层是否改动由 CI/review 校验)。 +- 审计测试断言:整数版本从 1 到当前最大值连续(`RETIRED_HOLES = {132, 133}` 内的号段除外)、无重复文件名、命名正则合规、历史文件校验和可复算稳定。 +- 修改任何已部署历史迁移会破坏 Flyway checksum,属违规;由本盘点测试 + code review 把关(git 层是否改动由 CI/review 校验)。 diff --git a/backend-java/src/main/resources/db/V136__web_config_add_is_latest.sql b/backend-java/src/main/resources/db/V136__web_config_add_is_latest.sql new file mode 100644 index 000000000..fd74fdcc1 --- /dev/null +++ b/backend-java/src/main/resources/db/V136__web_config_add_is_latest.sql @@ -0,0 +1,60 @@ +-- V136: web_config(桌面客户端升级包版本表)增加 is_latest 显式标记 +-- +-- 编号说明:本文件最初写作 V132,但生产 flyway_schema_history 已执行到 V135 +-- (V134/V135 于 2026-09-25 落库)。应用未开 out-of-order,低号新迁移会让 +-- validate-on-migrate 报 "Detected resolved migration not applied to database" 并启动失败, +-- 因此顺排到 V136。 +-- +-- 背景:这张表只追加、从不记录「哪一条是最新版」,读取侧靠 +-- ORDER BY created_at DESC, id DESC 现场算(SoftwareVersionService#latestSoftwareVersion)。 +-- 只要有人补插一条 created_at 较早的行(回滚发布、运维脚本补录历史版本), +-- 现场算出来的「最新版」就会退回去,而桌面端 APP_UPDATE_URL=/api/version/latest +-- 会把全体客户端指向那个旧包——且不会有任何报错。 +-- 数字人版本表 biz_digital_human_version 早已用 is_latest 显式标记规避同一问题 +-- (并有 deleteVersion 拒绝删最新的保护),这里与它对齐。 +-- +-- 存量回填:只把「迁移前现场算出来的那一条」标成 1。因此本迁移执行前后, +-- /api/version/latest 的返回值逐字节一致,不会把任何客户端切到别的版本。 +-- +-- 不加索引:本表 62 行,全表扫描成本可忽略,加索引属无收益的负担。 +-- +-- 风险:单表 62 行,ADD COLUMN 与单行 UPDATE 均秒级完成。 +-- 上线窗口:无锁窗口顾虑,随双节点滚动发布正常执行即可;但因本地/CI 无库不跑 migrate, +-- 首次执行发生在生产启动期,建议先发一台、确认下方验证 SQL 通过后再发第二台。 +-- 回滚:ALTER TABLE `web_config` DROP COLUMN `is_latest`; +-- +-- 验证 SQL(迁移后执行,三项都应命中): +-- SHOW COLUMNS FROM `web_config` LIKE 'is_latest'; +-- -> 期望 1 行,Type=tinyint(1),Default=0 +-- SELECT COUNT(*) AS flagged FROM `web_config` WHERE `is_latest` = 1; +-- -> 期望恰好 1(多行说明标记被写坏,读取侧虽有 LIMIT 1 兜底但仍应修数据) +-- SELECT `id`, `version`, `file_url` FROM `web_config` WHERE `is_latest` = 1; +-- -> 期望与迁移前 SELECT ... ORDER BY created_at DESC, id DESC LIMIT 1 同一行 +-- (迁移编写时核对为 id=260 / 4.0.32;实际以执行时刻的 created_at 最新行为准, +-- 本迁移的回填语句就是按该排序取一行,不写死 id) + +SET @db_name = DATABASE(); + +SET @col_exists := ( + SELECT COUNT(*) FROM information_schema.COLUMNS + WHERE TABLE_SCHEMA = @db_name AND TABLE_NAME = 'web_config' AND COLUMN_NAME = 'is_latest' +); +SET @sql := IF(@col_exists = 0, + 'ALTER TABLE `web_config` ADD COLUMN `is_latest` TINYINT(1) NOT NULL DEFAULT 0 COMMENT ''是否最新版(全表至多一行为1)'' AFTER `file_url`', + 'SELECT 1' +); +PREPARE stmt FROM @sql; +EXECUTE stmt; +DEALLOCATE PREPARE stmt; + +-- 回填:仅在还没有任何一行被标记时执行,重复执行不会把运维手工设定的标记冲掉。 +-- 用 UPDATE ... ORDER BY ... LIMIT 1 而不是子查询:单表更新写法最直白, +-- 也不会碰到 MySQL 的「不能在 UPDATE 的子查询里引用同一张表」(errno 1093)。 +SET @flagged := (SELECT COUNT(*) FROM `web_config` WHERE `is_latest` = 1); +SET @sql := IF(@flagged = 0, + 'UPDATE `web_config` SET `is_latest` = 1 ORDER BY `created_at` DESC, `id` DESC LIMIT 1', + 'SELECT 1' +); +PREPARE stmt FROM @sql; +EXECUTE stmt; +DEALLOCATE PREPARE stmt; diff --git a/backend-java/src/main/resources/db/V137__hide_redundant_indexes_invisible.sql b/backend-java/src/main/resources/db/V137__hide_redundant_indexes_invisible.sql new file mode 100644 index 000000000..69bc94650 --- /dev/null +++ b/backend-java/src/main/resources/db/V137__hide_redundant_indexes_invisible.sql @@ -0,0 +1,194 @@ +-- V137: 把「列是另一索引严格前缀」的冗余二级索引置为 INVISIBLE(只隐藏,不删除) +-- +-- 编号说明:原为 V133,因生产已执行到 V135 且应用未开 out-of-order,顺排到 V137。 +-- +-- 判定原则同 V121 / V123:被隐藏索引的列集合是另一个索引的严格左前缀, +-- 凡是能用它的查询都能由保留的那个索引完成,读能力无损失。 +-- 本次同样用前缀包含关系从线上 information_schema.STATISTICS 反查得出,共 20 个(18 张表)。 +-- +-- 与 V121/V123 的差别:这次用 INVISIBLE 而不是 DROP。 +-- 前缀规则保证的是「可用性」,不保证「代价相同」——需要覆盖扫描(只用前缀里那几列)的查询, +-- 用窄索引扫的页更少;换成宽索引可能变慢。线上我没有 performance_schema 读权限 +-- (aiimage 账号被 1142 拒绝),无法先量出哪些查询真在做覆盖扫描, +-- 所以先隐藏观察:影响只是执行计划换索引,出问题一条语句即可还原,不需要重建索引。 +-- 观察 1~2 周、慢日志无新增退化后再单独追加 V138 执行 DROP(V134/V135 已被占用)。 +-- +-- 为什么值得做:这些表的索引明显多于其体积(全库 226 个索引 / 62 张表), +-- 而慢日志里锁等待最集中的正是 biz_task_file_job(557 条、峰值 51s)—— +-- 少维护一个二级索引就少一份写放大与更短的持锁时间。 +-- +-- 风险:ALTER INDEX ... INVISIBLE 是纯元数据操作,秒级完成、不重建表、不锁数据。 +-- 每条都带 information_schema 存在性判断,索引不存在时自动跳过(开发库/副本库缺索引不会卡住启动)。 +-- +-- 验证 SQL: +-- SELECT COUNT(*) FROM information_schema.STATISTICS +-- WHERE TABLE_SCHEMA=DATABASE() AND IS_VISIBLE='NO'; +-- -> 期望 = 20(本迁移隐藏的个数,加上历史可能为 0 的存量) +-- SELECT TABLE_NAME, INDEX_NAME FROM information_schema.STATISTICS +-- WHERE TABLE_SCHEMA=DATABASE() AND IS_VISIBLE='NO' ORDER BY TABLE_NAME; +-- 上线窗口:任意时段均可(纯元数据);仍建议按 runbook 先发一台。 +-- 回滚(一条语句全部还原):见本文件末尾 ROLLBACK 注释块。 +-- +-- 模板:docs/flyway-migration-template.md(task-192) + +-- biz_collect_data_item.idx_task_id 列(task_id) 由 uk_task_row 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_collect_data_item` ALTER INDEX `idx_task_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_collect_data_item' AND INDEX_NAME = 'idx_task_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_file_result.idx_biz_file_result_module_user_created 列(module_type/user_id/created_at) 由 idx_file_result_patrol_history 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_file_result` ALTER INDEX `idx_biz_file_result_module_user_created` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_file_result' AND INDEX_NAME = 'idx_biz_file_result_module_user_created'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_patrol_delete_condition.idx_patrol_delete_condition_user_id 列(user_id) 由 uk_patrol_delete_condition_user_text 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_patrol_delete_condition` ALTER INDEX `idx_patrol_delete_condition_user_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_patrol_delete_condition' AND INDEX_NAME = 'idx_patrol_delete_condition_user_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_patrol_delete_shop_candidate.idx_user_id 列(user_id) 由 uk_user_shop 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_patrol_delete_shop_candidate` ALTER INDEX `idx_user_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_patrol_delete_shop_candidate' AND INDEX_NAME = 'idx_user_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_price_track_shop_candidate.idx_user_id 列(user_id) 由 uk_user_shop 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_price_track_shop_candidate` ALTER INDEX `idx_user_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_price_track_shop_candidate' AND INDEX_NAME = 'idx_user_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_product_risk_shop_candidate.idx_user_id 列(user_id) 由 uk_user_shop 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_product_risk_shop_candidate` ALTER INDEX `idx_user_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_product_risk_shop_candidate' AND INDEX_NAME = 'idx_user_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_query_asin_shop_candidate.idx_user_id 列(user_id) 由 uk_user_shop_name 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_query_asin_shop_candidate` ALTER INDEX `idx_user_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_query_asin_shop_candidate' AND INDEX_NAME = 'idx_user_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_shop_data_crawl_item.idx_shop_data_crawl_item_shop_date 列(shop_name/business_date) 由 idx_shop_data_crawl_item_batch 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_shop_data_crawl_item` ALTER INDEX `idx_shop_data_crawl_item_shop_date` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_shop_data_crawl_item' AND INDEX_NAME = 'idx_shop_data_crawl_item_shop_date'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_shop_data_crawl_shop_candidate.idx_shop_data_crawl_candidate_user 列(user_id) 由 uk_shop_data_crawl_candidate_user_shop 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_shop_data_crawl_shop_candidate` ALTER INDEX `idx_shop_data_crawl_candidate_user` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_shop_data_crawl_shop_candidate' AND INDEX_NAME = 'idx_shop_data_crawl_candidate_user'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_shop_manage.idx_created_by_id 列(created_by_id) 由 idx_created_by_id_id 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_shop_manage` ALTER INDEX `idx_created_by_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_shop_manage' AND INDEX_NAME = 'idx_created_by_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_shop_manage.idx_group_id 列(group_id) 由 idx_group_id_id 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_shop_manage` ALTER INDEX `idx_group_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_shop_manage' AND INDEX_NAME = 'idx_group_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_shop_manage_group.idx_user_id 列(user_id) 由 uk_user_id 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_shop_manage_group` ALTER INDEX `idx_user_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_shop_manage_group' AND INDEX_NAME = 'idx_user_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_shop_match_shop_candidate.idx_user_id 列(user_id) 由 uk_user_shop 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_shop_match_shop_candidate` ALTER INDEX `idx_user_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_shop_match_shop_candidate' AND INDEX_NAME = 'idx_user_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_similar_asin_filter_condition.idx_similar_asin_filter_condition_user_id 列(user_id) 由 uk_similar_asin_filter_condition_user_hash 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_similar_asin_filter_condition` ALTER INDEX `idx_similar_asin_filter_condition_user_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_similar_asin_filter_condition' AND INDEX_NAME = 'idx_similar_asin_filter_condition_user_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_skip_price_asin.idx_group_shop_name 列(group_id/shop_name) 由 idx_group_shop_asin_de 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_skip_price_asin` ALTER INDEX `idx_group_shop_name` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_skip_price_asin' AND INDEX_NAME = 'idx_group_shop_name'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_task_file_job.idx_file_job_module_type_result 列(module_type/job_type/result_id) 由 idx_task_file_job_patrol_history_lookup 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_task_file_job` ALTER INDEX `idx_file_job_module_type_result` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_task_file_job' AND INDEX_NAME = 'idx_file_job_module_type_result'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_task_file_job.idx_file_job_task 列(task_id/module_type) 由 uk_file_job_scope 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_task_file_job` ALTER INDEX `idx_file_job_task` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_task_file_job' AND INDEX_NAME = 'idx_file_job_task'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_task_result_payload.idx_task_module_scope 列(task_id/module_type/scope_hash) 由 uk_task_scope_submission 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_task_result_payload` ALTER INDEX `idx_task_module_scope` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_task_result_payload' AND INDEX_NAME = 'idx_task_module_scope'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- biz_withdraw_shop_candidate.idx_user_id 列(user_id) 由 uk_user_shop_name 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `biz_withdraw_shop_candidate` ALTER INDEX `idx_user_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'biz_withdraw_shop_candidate' AND INDEX_NAME = 'idx_user_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- image_history.idx_image_history_user_id 列(user_id) 由 idx_user_created 覆盖 +SET @s := (SELECT IF(COUNT(*) > 0, + 'ALTER TABLE `image_history` ALTER INDEX `idx_image_history_user_id` INVISIBLE', 'SELECT 1') + FROM information_schema.STATISTICS + WHERE TABLE_SCHEMA = DATABASE() AND TABLE_NAME = 'image_history' AND INDEX_NAME = 'idx_image_history_user_id'); +PREPARE st FROM @s; EXECUTE st; DEALLOCATE PREPARE st; + +-- ===================== ROLLBACK(全部还原为可见) ===================== +-- ALTER TABLE `biz_collect_data_item` ALTER INDEX `idx_task_id` VISIBLE; +-- ALTER TABLE `biz_file_result` ALTER INDEX `idx_biz_file_result_module_user_created` VISIBLE; +-- ALTER TABLE `biz_patrol_delete_condition` ALTER INDEX `idx_patrol_delete_condition_user_id` VISIBLE; +-- ALTER TABLE `biz_patrol_delete_shop_candidate` ALTER INDEX `idx_user_id` VISIBLE; +-- ALTER TABLE `biz_price_track_shop_candidate` ALTER INDEX `idx_user_id` VISIBLE; +-- ALTER TABLE `biz_product_risk_shop_candidate` ALTER INDEX `idx_user_id` VISIBLE; +-- ALTER TABLE `biz_query_asin_shop_candidate` ALTER INDEX `idx_user_id` VISIBLE; +-- ALTER TABLE `biz_shop_data_crawl_item` ALTER INDEX `idx_shop_data_crawl_item_shop_date` VISIBLE; +-- ALTER TABLE `biz_shop_data_crawl_shop_candidate` ALTER INDEX `idx_shop_data_crawl_candidate_user` VISIBLE; +-- ALTER TABLE `biz_shop_manage` ALTER INDEX `idx_created_by_id` VISIBLE; +-- ALTER TABLE `biz_shop_manage` ALTER INDEX `idx_group_id` VISIBLE; +-- ALTER TABLE `biz_shop_manage_group` ALTER INDEX `idx_user_id` VISIBLE; +-- ALTER TABLE `biz_shop_match_shop_candidate` ALTER INDEX `idx_user_id` VISIBLE; +-- ALTER TABLE `biz_similar_asin_filter_condition` ALTER INDEX `idx_similar_asin_filter_condition_user_id` VISIBLE; +-- ALTER TABLE `biz_skip_price_asin` ALTER INDEX `idx_group_shop_name` VISIBLE; +-- ALTER TABLE `biz_task_file_job` ALTER INDEX `idx_file_job_module_type_result` VISIBLE; +-- ALTER TABLE `biz_task_file_job` ALTER INDEX `idx_file_job_task` VISIBLE; +-- ALTER TABLE `biz_task_result_payload` ALTER INDEX `idx_task_module_scope` VISIBLE; +-- ALTER TABLE `biz_withdraw_shop_candidate` ALTER INDEX `idx_user_id` VISIBLE; +-- ALTER TABLE `image_history` ALTER INDEX `idx_image_history_user_id` VISIBLE; diff --git a/backend-java/src/test/java/com/nanri/aiimage/config/MigrationInventoryTest.java b/backend-java/src/test/java/com/nanri/aiimage/config/MigrationInventoryTest.java index 448e60cd6..3de7e1881 100644 --- a/backend-java/src/test/java/com/nanri/aiimage/config/MigrationInventoryTest.java +++ b/backend-java/src/test/java/com/nanri/aiimage/config/MigrationInventoryTest.java @@ -8,6 +8,7 @@ import java.nio.file.Files; import java.nio.file.Path; import java.security.MessageDigest; import java.util.ArrayList; +import java.util.Collections; import java.util.Comparator; import java.util.HashMap; import java.util.HashSet; @@ -23,7 +24,7 @@ import static org.junit.jupiter.api.Assertions.assertTrue; /** * task-193:历史迁移盘点审计(只读)。 - * 校验 src/main/resources/db 版本化迁移:整数版本 1..max 连续、无重复、命名合规、 + * 校验 src/main/resources/db 版本化迁移:整数版本 1..max 连续(RETIRED_HOLES 除外)、无重复、命名合规、 * 历史小版本(V25_1)被识别、校验和可复算稳定;产出 docs/migration-inventory.md 快照已提交。 */ class MigrationInventoryTest { @@ -66,15 +67,28 @@ class MigrationInventoryTest { return list; } + /** + * 已在生产 flyway_schema_history 中占位、但本地文件被改名让位的版本号。 + * 生产 131 之后直接装了 134/135(2026-09-25 20:46:16),132/133 从未落库; + * 而 Flyway 未开 out-of-order,把新迁移编号改回 132/133 会导致启动期 + * "resolved migration not applied" 失败,所以这个洞只能永久保留、不能回填。 + * 后果:新迁移只能取当前最大值之上的号(详见 docs/migration-inventory.md)。 + */ + private static final Set RETIRED_HOLES = Set.of(132, 133); + @Test void integerVersionsSequentialFromOne() throws IOException { List all = parseAll(versionFiles()); List integers = all.stream().filter(Migration::isInteger) .map(Migration::major).sorted().toList(); - for (int i = 0; i < integers.size(); i++) { - assertEquals(i + 1, integers.get(i), "整数版本应 1..N 连续,出现断号"); + Set actual = new HashSet<>(integers); + assertTrue(Collections.disjoint(actual, RETIRED_HOLES), "退役号段不应出现本地迁移文件"); + int max = integers.get(integers.size() - 1); + for (int v = 1; v <= max; v++) { + assertTrue(actual.contains(v) || RETIRED_HOLES.contains(v), + "整数版本应 1..max 连续(除已登记的退役洞),缺 V" + v); } - assertEquals(integers.size(), integers.get(integers.size() - 1), "整数版本应以 max 收尾且覆盖 1..max"); + assertEquals(max - RETIRED_HOLES.size(), integers.size(), "不应有重复版本号占位"); } @Test @@ -118,8 +132,14 @@ class MigrationInventoryTest { Path doc = Path.of(System.getProperty("user.dir"), "docs/migration-inventory.md"); assertTrue(Files.exists(doc), "盘点文档应存在并随仓库提交"); String text = Files.readString(doc); - assertTrue(text.contains("V108"), "文档应记录最新版本"); + int maxMajor = parseAll(versionFiles()).stream().filter(Migration::isInteger) + .mapToInt(Migration::major).max().orElse(0); + assertTrue(text.contains("V" + maxMajor), "文档应记录最新版本 V" + maxMajor); assertTrue(text.contains("25_1") || text.contains("V25_1"), "文档应记录历史小版本"); + for (int hole : RETIRED_HOLES) { + assertTrue(text.contains(String.valueOf(hole)), + "文档应记录退役空号 V" + hole + " 的来历,否则后来人会试图回填该号"); + } } @Test