Define the caller surface of the localOnly write option

未關閉
#765 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 4 天內回覆

還沒有人認領這個 Issue。

評估

難度
2/5
預估耗時
1-3 小時
新手友好度
52/100
Issue 類型
文件
描述清晰度
基本清楚
活躍度
活躍
領域
documentation

研究方向

Start with reference/replication/residency.md, then read the current source of linked PR #753 to see how the localOnly write option is described for internal callers. Clarify that caller surface without adding an operations-API field or expanding the runtime contract. Done means the documentation or scoped test reflects the internal write option accurately and does not reopen the parent sharding decisions.

由索引模型根據 Issue 內容生成。

描述

Deferred from the closing review of #753 for declarative sharding (Pro #980). The owner explicitly scoped this root cause out of the closing implementation batch.

Current assessment: Clarify the internal caller write option; do not invent an operations-API field.

Owning path: reference/replication/residency.md. Review lines move as the companion branches integrate main; use the linked PR's current source.

Follow-up: Implement and verify the scoped documentation or test improvement without expanding the current runtime contract.

This issue does not reopen #980's approved primary-key-only scope, complete-history requirement, or ban on write serialization. It does not block the current drafts. No release or backport is committed; milestone is intentionally unset. Found through source review and synthetic tests; there is no customer-specific incident evidence.

Triage: P3; effort Low; type Task. Low-priority follow-up: no demonstrated correctness failure or new release requirement. This is deliberately below the parent reliability priority.

Finding IDs: a8c85b56b9b3, 5b8acf33e644.

Review-Deferral: 0e3c268e20c6b07c severity=nit category=documentation

Review-Deferral: be8a7047ffc8505a severity=nit category=documentation

🤖 Generated by OpenAI Codex; posted via @kriszyp.

主要語言
MDX
星號
9
分支
9
平均合併
5 天 5 小時
30 天內合併 PR
48

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

HarperFast/documentation 的其他 Issue

查看 HarperFast/documentation 的全部 Issue

相似的 Issue

更多 Documentation Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。