Define the caller surface of the localOnly write option

Aperta
#765 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
52/100
Tipo di issue
Documentazione
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
documentation

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
MDX
Stelle
9
Fork
9
Merge medio
5g 5h
PR unite (30g)
48

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di HarperFast/documentation

Tutte le issue di HarperFast/documentation

Issue simili

Altre issue su Documentation

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.