archer import replays a sealed archive into an existing table: shard selection (`--select`), SHA-256 pre-verification, idempotent modes (`ignore`/`insert`/`replace`), and both LOAD DATA and batched-INSERT engines. It reads manifest.jsonl strictly so corruption is reported instead of skipped, and supports --dry-run, --allow-partial, and per-shard workers. --bulk-delete no longer rejects --shard-by date. Range deletion now derives its bounds from the chunk's actual keys (date scanners rewrite LastKey into a resumption cursor) and keeps safe-auto-increment semantics by excluding the current max key. A startup warning documents the monotonic-shard-column assumption. Also splits CLI/format/sharding/progress/safety reference docs out of the README, and adds the corresponding OpenSpec change artifacts. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
MODIFIED Requirements
Requirement: 参数依赖与互斥
系统 MUST 校验以下规则:--shard-by date 必须有 --shard-column;--shard-by count|none 不得带 --shard-column;--shard-rows 仅在 --shard-by count 或 date 时有效;--bulk-delete 依赖 --purge;普通插入、--insert-ignore、--replace 三者互斥;--compress-level MUST 在 1–9 范围内;--compress none 与非默认档位同时出现时 MUST 视为配置错误。违反时 MUST 在启动阶段报错。
Scenario: 数量模式误传日期列
- WHEN
--shard-by count同时带上--shard-column - THEN 系统报错,说明该参数仅在日期模式下有效
Scenario: 未启用 purge 却要求 bulk-delete
- WHEN 用户指定
--bulk-delete但未指定--purge - THEN 系统报错,说明 bulk-delete 必须配合 purge
Scenario: 日期模式使用 bulk-delete
- WHEN 用户同时指定
--shard-by date、--shard-column、--purge与--bulk-delete - THEN 系统通过启动校验,并在开始扫描前打印区间删除的安全前提警告
Scenario: 插入模式互斥
- WHEN 用户同时指定普通插入、
--insert-ignore与--replace中的多项 - THEN 系统在启动阶段报错