Verify archived v4 status and replication documentation against released behavior
维护者通常 4 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
调研方向
Start with the three archived v4 pages named in the issue: reference_versioned_docs/version-v4/operations-api/operations.md, replication/clustering.md, and replication/overview.md. Check the released v4 core and Pro source at the applicable tag for set_status persistence, cluster_status response field names, and the replication defaults for drop_database, drop_table, and drop_attribute, using a disposable runtime where source is inconclusive. Done means recording the tag, commit, and evidence for each contract, then either correcting mismatched prose or closing the audit with evidence that the wording is accurate.
由索引模型根据 Issue 内容生成。
描述
Page or URL
reference_versioned_docs/version-v4/operations-api/operations.md(set_statuspersistence)reference_versioned_docs/version-v4/replication/clustering.md(cluster_statusfield names)reference_versioned_docs/version-v4/replication/overview.md(destructive schema-operation replication)
What's wrong?
The v5 reliability-guide review in #671 identified analogous statements in the archived v4 reference whose released behavior has not been verified. This is an investigation task, not a confirmed v4 defect: v5 behavior alone is not evidence that the v4 text is wrong. The repository instructions keep archived-version changes separate from current v5 work.
Check the three contracts against the applicable released v4 core/Pro source and, where source is inconclusive, a disposable runtime. Record the exact tag/commit and evidence for status persistence, cluster-status response fields, and replication defaults for drop_database, drop_table, and drop_attribute. Correct archived prose only where that evidence shows a mismatch; otherwise close this audit with the evidence that the current wording is accurate.
Priority: P3. This is an off-roadmap documentation audit with no confirmed defect or customer incident. Effort: Low; the audit is bounded to three named contracts. No matching archived-v4 epic or committed release was found, so parent and milestone are unset.
Review-Deferral: 0d6e0904b0f240aa severity=minor category=documentation
🤖 Generated by OpenAI Codex; posted via @Ethan-Arrowood.
- 主要语言
- MDX
- 星标
- 9
- 派生
- 9
- 平均合并
- 5 天 5 小时
- 30 天内合并 PR
- 48
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
HarperFast/documentation 的其他 Issue
-
Document http.maxRequestBodySize (REST, MCP application endpoint, and operations API body limits)未关闭
难度 2/5 1-3 小时 新手友好度 88/100
HarperFast/documentation#806 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
HarperFast/documentation#803 ·
维护者通常 4 天内回复
-
content
难度 2/5 1-3 小时 新手友好度 65/100
HarperFast/documentation#785 ·
维护者通常 4 天内回复
-
content
难度 2/5 半天 新手友好度 68/100
HarperFast/documentation#770 ·
维护者通常 4 天内回复
-
content
难度 2/5 1-3 小时 新手友好度 74/100
HarperFast/documentation#769 ·
维护者通常 4 天内回复
查看 HarperFast/documentation 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
we-promise/sure#5191 ·
维护者通常 1 天内回复
-
custom-types postgres
难度 2/5 1-3 小时 新手友好度 77/100
tursodatabase/turso#11908 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
CopilotKit/OpenBot#1747 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
can4hou6joeng4/boss-agent-cli#1477 ·
维护者通常 1 天内回复
-
bug ux
难度 2/5 1-3 小时 新手友好度 70/100
mithilp/keybuddies#66 ·