Skip to content

[DOC-14519][AI] Point durable writes note at the correct section - #4157

Draft
TimLFletcher wants to merge 1 commit into
release/8.0from
DOC-14519
Draft

[DOC-14519][AI] Point durable writes note at the correct section#4157
TimLFletcher wants to merge 1 commit into
release/8.0from
DOC-14519

Conversation

@TimLFletcher

@TimLFletcher TimLFletcher commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Partially addresses DOC-14519. Do not close the ticket on merge.

What changed

modules/introduction/partials/new-features-80.adoc (included by introduction/whats-new.adoc), line 97.

The 8.0 "What's New" entry for Optionally Maintain Durable Write Availability After Losing Majority Due to Failover linked to a section about ephemeral buckets:

-See xref:learn:clusters-and-availability/automatic-failover.adoc#auto-failover-and-ephemeral-buckets[Auto-Failover and Ephemeral Buckets] ...
+See xref:learn:data/durability.adoc#maintaining-durable-writes[Maintaining Durable Writes During Replica Failovers] ...

The new target is the section that actually describes the feature.

What this does NOT fix

The ticket reports two problems. The second is that line 83 calls this a cluster-level option while the core documentation describes a bucket-level setting. The ticket itself says this needs confirming with Engineering before the wording changes, so it is deliberately left alone here.

Verification

Anchor [#maintaining-durable-writes] confirmed present at modules/learn/pages/data/durability.adoc:373. Checked by inspection, because Antora validates xref page targets but not #fragment anchors.

Build diffed against a clean-tree baseline of release/8.0:

PASS[docs-server @ DOC-14519]: no new build diagnostics.

🤖 Generated with Claude Code

The 8.0 "What's New" entry for maintaining durable write availability
linked to Auto-Failover and Ephemeral Buckets in automatic-failover.adoc.
It now links to Maintaining Durable Writes During Replica Failovers in
durability.adoc, which is the section describing the feature.

Does not address the second half of the ticket, which reports the feature
as cluster-level where the core documentation calls it bucket-level. The
ticket asks for that to be confirmed with Engineering first.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant