Define the caller surface of the localOnly write option

Aberta
#765 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 4 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
52/100
Tipo de issue
Documentação
Clareza
Razoavelmente clara
Status de atividade
Ativa
Domínio
documentation

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
MDX
Estrelas
9
Forks
9
Merge médio
5d 5h
PRs com merge (30d)
48

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de HarperFast/documentation

Todas as issues de HarperFast/documentation

Issues semelhantes

Mais issues de Documentation

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.