CASSANDRA-21342: Long-tail xref follow-up (trunk)#4810
Open
pmcfadin wants to merge 1 commit into
Open
Conversation
Follow-up to the umbrella patch for CASSANDRA-21342 (merged 2026-05-14). Closes the long-tail of trunk xref errors that remained after the first wave landed. Mechanical retargets only; no prose was rewritten and no pages were added or removed. Anchors that did not exist are added with the project's existing [[anchor]] convention. Edit classes: * Module-prefix xrefs: bare/partial paths -> cassandra:-qualified * Moved-page xrefs: retarget to current home on trunk * Filename typo: defintions.adoc -> definitions.adoc * Extension: .html -> .adoc; writetime retargeted to functions.adoc * nodetool xrefs: qualify to cassandra:managing/tools/nodetool/ * Anchors: add three missing [[anchor]] targets and retarget the xrefs that point at them For every still-existing anchor target the destination page and [[anchor]] (or generated section id) were grep-verified on upstream/trunk before the edit. Triage was driven by the 2026-04-21 Antora 3 baseline (Jenkins apache#2752); patterns where no source file on trunk still references the old target were treated as already-closed and not touched. Build verification: cassandra-website built locally with Antora 3 against this branch as the cassandra source drops trunk-level errors from 161 (baseline) to 3. The three remaining errors are all in cassandra-website source (blog posts + main-nav.adoc) and out of scope for this patch. Drafting and triage were performed with AI assistance (Anthropic Claude); the change set is reviewable as mechanical xref retargets and anchor additions. Source provenance per ASF generative tooling guidance. patch by Patrick McFadin; reviewed by TBD for CASSANDRA-21342
pmcfadin
force-pushed
the
CASSANDRA-21342-trunk-followup
branch
from
cac55a5 to
dc1186b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to the umbrella patch for CASSANDRA-21342 (merged 2026-05-14). Closes the long-tail of broken xref errors that remained on
trunkafter the first wave landed.Mechanical retargets only — no prose was rewritten and no pages were added or removed. Anchors that did not exist are added with the project's existing
[[anchor]]convention.Edit classes
cassandra:-qualified)defintions.adoc->definitions.adoc).html->.adoc; writetime retargeted tofunctions.adocnodetoolxrefs qualified tocassandra:managing/tools/nodetool/(generated targets)[[anchor]]targets and retarget the xrefs that point at them26 files changed total, +40 / -37.
Verification
For every still-existing anchor target, the destination page and explicit
[[anchor]](or auto-generated section id) were grep-verified onupstream/trunkbefore the edit. Triage was driven by the 2026-04-21 Antora 3 baseline (Jenkins #2752); patterns where no source file ontrunkstill references the old target were treated as already-closed and not touched.Build evidence
cassandra-website built locally with Antora 3 against this branch as the cassandra source:
The 3 remaining errors are all in cassandra-website source (two blog posts referencing
Cassandra:cassandra:architecture/overview.adoc, andmain-nav.adocreferencingCassandra::index.adoc) — out of scope for this patch on the cassandra repo.Not included
About ten additional broken xrefs require content decisions and are deferred to a separate workstream alongside the
master@_:ROOT:bugs.adoc/contactus.adocdecision (Accord index stub, compression-options retarget,_2i-*partial-prefix resolution, thecyclist_*-table.adocexample references, drop-materialized-view stub, the_/download.adoccross-component xref). They are mechanically distinct: they need either a new page, an external link, or a prose rewrite — not a retarget.Generated-page caveat
The four
nodetoolxrefs included point at generated pages thatgen-asciidocemits at Antora build time, so they cannot be grep-verified from a static checkout. The form matches existingnav.adocxrefs (e.g.cassandra:managing/tools/nodetool/nodetool.adoc) that have shipped without complaint. If any do not resolve at the next build, will fix in a follow-up.Forward-merge
cassandra-5.0,cassandra-4.1, andcassandra-4.0will receive applicable subsets after merge here, following the same convention as the previous CASSANDRA-21342 PR's forward-merges (committer push, no per-branch PR). Pattern-presence will be re-checked per branch.AI disclosure
Drafting and triage were performed with AI assistance (Anthropic Claude). The change set is reviewable as straightforward xref retargets and anchor additions. Source provenance per ASF generative tooling guidance.