Verify archived v4 status and replication documentation against released behavior

Ouverte
#732 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 4 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
35/100
Type d'issue
Documentation
Clarté
Plutôt claire
Activité
Active

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

content
Page or URL
  • reference_versioned_docs/version-v4/operations-api/operations.md (set_status persistence)
  • reference_versioned_docs/version-v4/replication/clustering.md (cluster_status field 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.

Langage dominant
MDX
Étoiles
9
Forks
9
Merge moyen
5 j 5 h
PR mergées (30 j)
48

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de HarperFast/documentation

Toutes les issues de HarperFast/documentation

Issues similaires

Plus d'issues Databases

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.